2 years ago

A few weeks ago a spec change for an application we’re working on forced us to refactor part of the codebase. It was food for thought about the flexibility granular interfaces provide, and choosing the right abstraction at the right time.

After the bundle is purchased, registrations need to be created for the underlying courses, not the bundle itself.

class Bundle implements Product, CreatesRegistrations { public function __construct( public array $courses ) { } public function createsRegistrationsFor(): array { return $this->courses; }}

If we want to know wether a product will create a registration, we have to check for both the Registrable and CreatesRegistrations interfaces.