Weave Code
Dependent Filter Laravel Package
awesome-nova/dependent-filter
Nova dependent filter lets one filter's options update based on another's selection, keeping resource filters interactive and context-aware. It supports chained selects, custom queries, and flexible configuration for building responsive admin filtering.
Dependent filters for Laravel Nova
Frequently asked questions about Dependent Filter
- What does awesome-nova/dependent-filter do in Laravel Nova?
- It lets one Nova filter's options update based on another filter's selection, so admin resource filters become interactive and context-aware. The package supports chained selects, custom queries, and flexible configuration for responsive admin filtering. It belongs in the Nova presentation and admin layer, not in core domain logic or public APIs.
- How do I install awesome-nova/dependent-filter in a Laravel Nova app?
- Install it through Composer using the package name, then follow the package's Nova service-provider and filter registration instructions for your Nova version. Because the last release was February 2019, confirm the exact install steps against your Laravel, PHP, and Nova stack before production use. Keep the registration isolated in your Nova admin setup rather than spreading dependency assumptions into application code.
- Is awesome-nova/dependent-filter compatible with current Laravel and Nova versions?
- You should not assume compatibility. The last release date of February 2019 strongly suggests it may target older Nova APIs, PHP versions, and frontend asset pipelines. Run a branch-based compatibility spike and verify Composer constraints, Nova version support, PHP support, and compiled frontend behavior. Treat it as incompatible until proven otherwise.
- How do I create a chained or cascading select filter in Nova with this package?
- Define the Nova filters and configure the dependency relationship so one filter's available options are driven by another filter's selection, following the package documentation for your Nova version. The package is intended for chained selects and context-aware admin filtering, but you should test empty selections, cleared selections, and dependent result sets. Keep the configuration isolated within your Nova service-provider registration.
- Can dependent-filter use custom queries for filter options?
- Yes, the package is described as supporting custom queries and flexible configuration for dependent filter options. Make sure those queries are efficient and that relevant database indexes exist as admin datasets and filter chains grow. Test custom query behavior with empty results and combined filter selections before rolling it out to admin users.
- What are the alternatives to awesome-nova/dependent-filter for dependent Nova filters?
- Start by checking whether native Nova filters or a small custom Nova filter can cover the exact dependent-filter behavior you need. Because this package is small in scope but stale and low-momentum, vendoring or forking it may be safer than depending on upstream. A custom in-house filter is often preferable when the dependency behavior is simple and upgrade ownership matters.
- Is awesome-nova/dependent-filter maintained and safe for production?
- It carries high abandonment risk because the last release was February 2019, stars are low, and community momentum appears limited. Treat it as a tactical admin UX accelerator rather than a strategic dependency. Pin the version, roll it out to admin users only, keep a fallback to native filters, and document an exit path before broader adoption.
- How should I test dependent filters before deploying to production?
- Run a compatibility spike in a branch against the exact Nova, Laravel, and PHP versions you use. Test filter registration, dependency behavior, empty-result handling, Composer conflicts, and frontend asset compatibility. Then stage an admin-only rollout with a feature flag and a fallback to standard filters, and add regression checks for the dependent-filter workflow.
- What Laravel and PHP versions does this package support?
- The package's Composer metadata and declared constraints are the source of truth for Laravel, PHP, and Nova support. The February 2019 release date suggests it may target older versions, so do not rely on the README alone. Verify compatibility with your target stack and compiled frontend pipeline before committing to it.
- Can I vendor or fork awesome-nova/dependent-filter if it is incompatible?
- Yes, vendoring or forking is reasonable if the package code is small and its license is permissive. Fork the minimal Nova filter code, keep it behind Nova service-provider registration, and assign an owner for upgrade testing when Nova or Laravel changes. Document the dependent-filter behavior and exit path so future maintainers do not have to reverse-engineer it.
Weaver
How can I help you explore Laravel packages today?