Filament Spatie Laravel Backup Laravel Package

Getting Started

Install the latest release (^1.2.7) so the new action-level notification-option toggle is available. Start by opening an existing action class—that is where notification options are declared and now where you can disable them per action. Your first use case: take an action that currently sends a notification with default options and disable one option (for example, email or SMS) directly on the action, then trigger it in a local route or test to confirm the notification behavior changes without touching global config.

Implementation Patterns

• Declare notification options on the action, then use the new disable capability to override them at runtime (the package’s new action method, e.g. disableNotificationOption('mail') or equivalent). Keep defaults in config and use action-level disabling for exceptions.
• Wrap action invocation in a service or queued job when the decision to disable options depends on user role, environment, or feature flags.
• Compose actions with Laravel notifications/events; disable options on the action rather than mutating the notification after dispatch.
• In tests, instantiate the action, disable an option, dispatch it, and assert with Notification::fake() that the expected channels were used or skipped.
• For reusable behavior, create a base action class that applies common disable rules and let concrete actions opt in.

Gotchas and Tips

• The feature is only in v1.2.7+; pin the version or check composer show before relying on it.
• Disabling a notification option from an action may not stop the notification from being dispatched—it only suppresses the selected option/channel. Verify the package’s semantics in its tests or docs.
• If options are cached or resolved from config, run php artisan config:clear after changes and avoid caching action instances with runtime-dependent disables.
• Actions resolved through the container should not capture request-specific state in constructors; pass disabling decisions as method arguments or via a context object.
• Use Notification::fake() and Event::fake() to isolate behavior; assert both the action outcome and the notification channels.
• Extension point: subclass the action or bind a custom action resolver if you need organization-wide defaults for disabled options.