Filament Jetstream Laravel Package

Getting Started

• Install the package via Composer (composer require mominalzaraa/filament-team-guard), then publish its config and any stubs/actions (php artisan vendor:publish --tag=filament-team-guard-config and the relevant actions tag).
• First place to look: the UpdatesTeamNames contract and the default UpdateTeamName Livewire component. These define how team name changes are delegated. Bind the contract in a service provider (AppServiceProvider or a dedicated provider) if you need custom behavior.
• First use case: add team name editing to a Filament panel backed by Jetstream teams, then override the default update path by binding your own UpdatesTeamNames implementation or publishing App\Actions\FilamentJetstream\UpdateTeamName.
• v2.1.1 is a patch release: it restores delegation to the contract for published UpdateTeamName components. Existing installs should upgrade and re-test custom team-name actions.

Implementation Patterns

• Contract binding for custom logic — Implement UpdatesTeamNames and bind it in a service provider. This centralizes validation, audit logging, or domain events when a team name changes, and keeps the Filament component free of business logic.
• Published action override — Publish App\Actions\FilamentJetstream\UpdateTeamName when you need to customize the Livewire-facing behavior (fields, authorization, redirects). Keep the action delegating to the UpdatesTeamNames contract so package upgrades do not break the flow.
• Testing delegation — In feature tests, bind a fake UpdatesTeamNames and assert the Livewire UpdateTeamName component calls it. This mirrors the regression tests added in v2.1.1 and protects against future direct $team->update() calls.
• Panel integration — Use the package’s Filament page/component inside a panel that already uses Jetstream’s team model. Verify the panel’s tenant resolution and the team model match Jetstream’s Team model.
• Upgrade workflow — After upgrading to v2.1.1, confirm that a custom published UpdateTeamName is actually invoked. A quick Log::info() inside the action or contract implementation is enough to verify the delegation path.

Gotchas and Tips

• v2.1.1 regression fix — Prior versions could bypass the UpdatesTeamNames contract when a published UpdateTeamName existed. If you customized team name updates before this release, re-test after upgrading; your custom action should now receive the call.
• Binding is required — If you implement a custom UpdatesTeamNames but forget to bind it, the default implementation is used. Check your service provider and run php artisan optimize:clear after changes.
• Namespace drift — Published actions live under App\Actions\FilamentJetstream\UpdateTeamName. If you rename or move the class, update the component’s resolution or republish the stub; otherwise the default path may run instead.
• Cache cliffs — Config, view, and route caches can mask a stale published component or contract binding. Clear caches when debugging “my custom action is not called.”
• Test isolation — The package’s test suite uses an isolated SQLite configuration. If you extend its tests, mirror that setup to avoid touching your development database.
• Debugging delegation — Log inside your UpdatesTeamNames implementation and inside the Livewire component. If only the component logs, the binding or published action is not being resolved as expected.