- What does petecoop/filament-toolbar-filters do?
- It adds toolbar filters to Filament tables, letting you place filter controls directly in the table toolbar instead of a separate filter panel. It integrates with Filament's existing filter API, so the filters you already define can be surfaced in the toolbar for quicker access. The package is a UI convenience layer rather than a new filtering engine.
- How do I install filament-toolbar-filters with Composer?
- Install it with composer require petecoop/filament-toolbar-filters. Like most Laravel packages it is expected to be auto-discovered through its service provider, and you may have the option to publish config or assets with vendor:publish. Check the repository README for the exact install steps and any Filament panel registration required.
- Which Laravel and Filament versions does this package support?
- The 0.1.0 release has empty release notes, so supported PHP, Laravel, and Filament version ranges are not explicitly documented. Before adopting, inspect the package's composer.json constraints for illuminate/* and filament/* requirements and confirm they match your pinned versions. A time-boxed spike in a test app is the fastest way to validate compatibility.
- Is version 0.1.0 stable enough for production use?
- Under SemVer, 0.x releases may introduce breaking changes in minor version bumps, so treat the public API as unstable until a 1.0.0 release. If you adopt it, pin an exact version and re-review on every upstream update. For production, weigh the convenience of toolbar filters against the maintenance cost of tracking a pre-1.0 dependency.
- Do toolbar filters work with my existing Filament table filters?
- Yes, the package integrates with Filament's filter API, so filters you already define on a table can be rendered in the toolbar. That means you generally do not need to rewrite filter logic; you adjust how and where the controls are displayed. Confirm the supported filter types for your Filament version in the README.
- How do I test that toolbar filters work in my application?
- Cover it with Filament's standard Livewire table tests: assert the toolbar filter controls render and that applying a filter narrows the query results. Because the package is pre-1.0 and its own test coverage is unknown, add your own regression tests around the filters you expose. Also verify behavior after each upstream minor release.
- What are the alternatives to using this Filament toolbar filter package?
- You can build toolbar filters yourself with Filament's filter API and custom table header or toolbar actions, which avoids an extra pre-1.0 dependency. Alternatively use Filament's built-in filter panel if the extra click is acceptable, or a broader admin panel package that already supports inline filters. Choose based on how much you value the toolbar UX versus dependency risk.
- What is the removal cost if we back out of this package?
- Because it is a Composer package registered through a service provider, removal is generally composer remove plus reverting any table code that references its toolbar filter classes. There is no indication of migrations or owned persisted state, so data rollback should not be a concern. Confirm in a spike whether it publishes config or registers container bindings you rely on.
- Is the package actively maintained and will the changelog improve?
- That cannot be determined from the artifact alone: 0.1.0 has empty release notes, which could indicate an early-but-active project or an abandoned experiment. Ask the maintainer about the roadmap, a planned 1.0.0, and whether future releases will be documented. Treat a populated changelog as a condition of adoption.
- Does filament-toolbar-filters require config publishing or migrations?
- The package is described as a toolbar filter UI extension, so migrations are unlikely, but the README should be checked for optional vendor:publish steps for config or assets. If any migrations exist, verify they are additive-only. Also identify what the service provider registers so you understand the removal cost and any container bindings.