Weave Code
Extra Filters Bundle Laravel Package
instacar/extra-filters-bundle
instacar/extra-filters-bundle adds practical extra filter types to Symfony admin listings, so you can narrow records by date ranges, statuses, and related values. Simple to configure and drop in, it makes large datasets easier to browse and manage.
At a glance
Frequently asked questions about Extra Filters Bundle
- What does instacar/extra-filters-bundle actually do?
- It adds practical extra filter types to admin and listing screens, letting users narrow records by date ranges, statuses, and related values. The goal is making large datasets easier to browse and manage. It is a query-filtering utility meant for list endpoints, admin grids, or reporting screens.
- Does instacar/extra-filters-bundle work with Laravel?
- Not natively. The package is described and versioned as a Symfony bundle, so it depends on the Symfony kernel, bundle registration, and Symfony HTTP and DI components rather than a Laravel service provider or Eloquent. In a Laravel app it is at best a PHP-level query helper that must be wired manually behind an internal filter contract or adapter.
- How do I install instacar/extra-filters-bundle with Composer?
- Composer installation itself is straightforward, but before adding it to a Laravel project confirm which PHP versions and Symfony component ranges v0.2.3 pins. Watch for duplicate or conflicting Symfony components that overlap with Laravel's own dependencies. Treat installation as a spike until you have proven the filter core runs outside the Symfony bundle bootstrap.
- Which Symfony and PHP versions does v0.2.3 support?
- The v0.2.3 release note says it added support for Symfony 6.2, which is the only compatibility signal in the changelog. PHP version constraints are undocumented, so you should inspect the composer.json of the tagged release yourself. Nothing in the release history indicates Laravel support.
- What license does instacar/extra-filters-bundle use?
- The license metadata reports NOASSERTION, meaning the actual license terms are unclear. This is the top technical risk because license ambiguity can block commercial distribution or internal policy approval. Resolve it with the maintainer before putting the package anywhere near a production dependency.
- Can the filtering logic be used standalone without the Symfony bundle?
- That is unresolved and is the key question for any Laravel evaluation. The package is bundle-coupled by design, and nothing in the release notes shows the filter core is usable on its own. You need a spike that proves the filtering classes work outside the Symfony kernel before committing.
- Is instacar/extra-filters-bundle production-ready?
- Treat it as a reference implementation or spike only. It is still on a 0.x version, has around 9 stars, zero dependents, a package score of about 0.435, and no public evidence of CI, static analysis, or meaningful test coverage. The typo-laden changelog also suggests light release QA.
- How does it handle untrusted input and query performance?
- Filter input handling is undocumented, so sanitize and validate anything that reaches the filter layer from user requests. Relationship filters and date ranges can add query complexity, so check the generated SQL and add indexes where needed. Do not expose the filters broadly without regression tests against your own datasets.
- What are the alternatives for filtering Laravel and Symfony admin listings?
- For Laravel, Eloquent query scopes, a dedicated query builder filter package, or an internal filter abstraction will be safer than adopting a Symfony bundle. For Symfony, custom Doctrine query builders or the built-in filters in admin bundles cover the same date range and status use cases. Both routes avoid the license and framework-mismatch risk here.
- Is instacar/extra-filters-bundle actively maintained?
- The only recent signal is a narrow Symfony 6.2 compatibility bump, not feature or maintenance work. With low stars, zero dependents, and a single contributor handle in the changelog, there is little evidence the package survives upgrade cycles. Plan a fallback in case it is abandoned.
Weaver
How can I help you explore Laravel packages today?