DI and actions

The facade is sugar — there are three equivalent entry points, and the choice is yours:

• The Contacts facade — the shortest, and the recommended default.
• The manager, injected through the constructor — the same API as an explicit dependency, with no static calls. RoundlyConsulting\Contacts\ContactsManager is the facade root, bound as a singleton.
• Actions — single-purpose classes with an execute() method, for composing into your own actions, jobs and commands.

Injecting the manager

Contacts::fake() swaps the manager binding, so constructor-injected code is recorded too:

use App\Models\User;
use RoundlyConsulting\Contacts\ContactsManager;
use RoundlyConsulting\Contacts\Models\Contact;

final readonly class AddWorkEmail
{
    public function __construct(private ContactsManager $contacts) {}

    public function __invoke(User $user, string $email): Contact
    {
        $contact = $this->contacts->for($user)->email($email)->label('Work')->primary()->add();

        $this->contacts->verification()->request($contact);

        return $contact;
    }
}

Running an action

Every write on the facade is one action, resolved from the container:

use RoundlyConsulting\Contacts\Actions\AddContactAction;
use RoundlyConsulting\Contacts\Actions\RequestContactVerificationAction;
use RoundlyConsulting\Contacts\DataTransferObjects\ContactData;
use RoundlyConsulting\Contacts\Enums\ContactType;

$contact = app(AddContactAction::class)->execute($user, new ContactData(ContactType::Email, '[email protected]'));
$token = app(RequestContactVerificationAction::class)->execute($contact);

Each action takes the owner or contact and a ContactData DTO where it needs one, and applies the same normalization, validation, primary handling and events as the facade. An action you call directly runs for real — Contacts::fake() records calls that go through the manager.