- How do I install awcodes/filament-quick-create in my Laravel Filament project?
- Run `composer require awcodes/filament-quick-create` and register the plugin in your `Panel` configuration using `QuickCreatePlugin::make()`. Ensure you’ve set up a custom Filament theme first, as the plugin requires it for CSS/Blade integration.
- Does this plugin work with Filament v3, v4, or v5? What’s the version mapping?
- Yes, the plugin supports Filament v2–v5 with strict version alignment: use `2.x` for Filament 2.x, `3.x` for 3.x, etc. Always pin the exact version in `composer.json` to avoid compatibility issues during updates.
- Can I customize which resources appear in the quick-create dropdown?
- Absolutely. Use `includes()` to whitelist specific resources or `excludes()` to blacklist them. Avoid mixing both methods, as they override each other. Example: `QuickCreatePlugin::make()->includes([PostResource::class])`.
- Will this plugin interfere with existing keyboard shortcuts in my Filament app?
- The plugin doesn’t enforce default shortcuts, but conflicts *may* occur if your app uses `command+shift+a` or similar. Test thoroughly with power users and adjust via custom JavaScript if needed.
- Does awcodes/filament-quick-create support custom create workflows (e.g., multi-step forms)?
- The plugin uses Filament’s default create modal/slide-over, which may not suit complex workflows. For advanced cases, override the `create` action in your resource or extend the plugin’s Blade views to tailor the UI.
- How does the plugin handle authorization? Will unauthorized users see restricted resources?
- The plugin respects Filament’s built-in authorization. Resources requiring `create` permissions won’t appear in the dropdown for unauthorized users. For edge cases (e.g., tenant-specific permissions), extend Filament’s `canAccessPanel()` or use custom gates.
- Is there a performance impact if I have 50+ resources in the dropdown?
- Large resource lists *may* slow dropdown rendering. Mitigate this by using `includes()` to limit options or test with `filament:optimize` to cache resource metadata. Monitor load times in staging before production.
- Can I style the quick-create dropdown to match my Filament theme?
- Yes, the plugin integrates with Filament’s custom theme system. Extend the provided Blade views or override CSS classes (e.g., `.filament-quick-create-dropdown`) in your theme’s assets. Check the `resources/views` folder for targetable components.
- What happens if Filament’s resource registration fails (e.g., during a partial outage)?
- The plugin gracefully falls back to an empty dropdown if resource registration errors occur. For critical applications, wrap the plugin registration in a try-catch block or add a fallback UI via Filament’s `panels::user-menu.before` hook.
- Are there alternatives to awcodes/filament-quick-create for quick-create functionality in Filament?
- For Filament v3+, consider `filament/spatie-laravel-resource-tools` (for bulk actions) or `filament/filament-actions` (custom buttons). For v2, `spatie/laravel-filament-actions` offers similar functionality. However, this plugin is the most lightweight for *pure* quick-create dropdowns.