- How do I install digital-creative/nova-slider-filter?
- Run composer require digital-creative/nova-slider-filter in a Laravel application that already has Laravel Nova installed. The package ships no service provider and no migrations, so there is nothing extra to register beyond Composer's autoloading. After installing, add the filter class to the filters() method of the Nova resource you want to filter and make sure Nova's assets are published or built as usual.
- Which Laravel Nova versions does nova-slider-filter support?
- The last tagged release is from October 2023, which predates Nova 5, so the safe assumption is Nova 4 era compatibility. Check the composer.json constraints for the declared Nova and PHP versions before committing to it. If you are on Nova 5, budget a short spike to confirm the Vue 3 based frontend still applies the filter correctly.
- How do I add a range slider filter to a Nova resource?
- Import the filter class and return an instance of it from your resource's filters() method, passing the min, max and target column options it expects. Nova then renders a slider in the filter panel, and the filter's apply() method scopes the index query, typically with whereBetween. Because it is a leaf-level UI extension, no application domain code needs to change.
- Does nova-slider-filter handle decimal and negative values?
- The overview only promises a range between a min and max value, and there is no visible test suite covering numeric edge cases. Before relying on it, verify decimals, negative numbers and exact boundary values against a known dataset. If your column is a decimal, confirm the slider step size and casting behave as expected rather than assuming integer semantics.
- Is nova-slider-filter compatible with Nova 5 and Vue 3?
- This is the highest-risk area: the package's last release predates Nova 5, and Nova's frontend moved from Vue 2 to Vue 3. The typical failure mode is a filter that renders but silently fails to apply, which is easy to miss in QA. Test on your exact Nova version in a disposable install and confirm the generated SQL before adopting it.
- What happens if a user only sets the minimum or only the maximum on the slider?
- Open-ended and inverted ranges are exactly the behaviour the package does not document, and there are no tests to confirm it. Test three cases explicitly: only a lower bound, only an upper bound, and a range where the handles are dragged past each other. If any of them produce a malformed whereBetween or an unscoped query, wrap or override the apply() method.
- Does the slider filter work with Nova lenses and metric scoping?
- Filters registered on a resource generally appear in lens views that inherit that resource's filters, but the package does not document lens behaviour, so treat it as unverified. Test the filter inside each lens and on any metric cards that read the same request parameters. If a lens builds its query differently, the whereBetween scope may need adapting or overriding.
- Is nova-slider-filter still maintained?
- It has a very small footprint: roughly 13 GitHub stars, no dependents and a last release in October 2023, so treat it as unmaintained source you are adopting rather than a vendor product. The licence is MIT, so forking is permitted and is the intended escape hatch. The practical approach is to vendor or wrap it behind your own filter class so a Nova upgrade can be fixed in hours instead of blocked upstream.
- What are the alternatives to nova-slider-filter for numeric range filtering?
- Nova ships native filter types, and for many cases a SelectFilter with preset buckets or two numeric inputs covers the same need without third-party code. Check whether your Nova version already includes a native range or interval filter before adding a dependency. A slider is a UX improvement, so if only one or two resources need it, the build-versus-adopt calculation often favours a native option.
- How do I verify the slider filter's SQL and parameter binding?
- Register the filter on a resource with a small known dataset, apply a range in the UI, and dump the query with DB::listen or Laravel Telescope to inspect the generated SQL. Confirm the bounds are passed as bound parameters rather than interpolated into the query string. Also confirm the filter is scoped to the intended column and does not leak into unrelated queries.