Weave Code
Value Filter Laravel Package
seoegypt/value-filter
A lightweight Laravel package for filtering incoming request values and query parameters. Apply clean, reusable filter rules to validate and sanitize data before it reaches your application logic, keeping controllers and services tidy.
Value Filter is a Laravel package for cleaning and normalizing input values before they reach your application logic. It provides a simple, configurable way to filter request data, strip unwanted characters, and enforce consistent formats—useful when you need lightweight sanitization separate from full validation.
- Chainable filter rules for common transformations (trim, lowercase, strip tags, digits-only)
- Works with FormRequest and raw input arrays
- Custom callback filters for project-specific rules
- Configurable defaults for consistent behavior across endpoints
- Framework-native, no external dependencies
Frequently asked questions about Value Filter
- What does seoegypt/value-filter actually do?
- Despite a description that suggests general input sanitization, the technical assessment places it as a Laravel Nova Resource filter for admin index screens. It shapes the Eloquent query behind a Nova index, mainly for discrete-value equality filtering such as status, role, or priority. It is not a validation or sanitization layer for form requests, jobs, or customer-facing APIs. Verify the class FQCN, key(), name(), and apply() semantics in src before writing code.
- Does value-filter work with Laravel FormRequest and raw input arrays?
- The advertised overview says it works with FormRequest and raw input arrays, but the TPM evaluation explicitly corrects that framing and says it is not a sanitization or validation layer for application code. Treat the FormRequest claim as unverified until you read the source. If you need request cleaning, use Laravel validation, FormRequest preparation, or an in-house sanitizer instead. Do not scope work against the marketing description alone.
- Do I need a Laravel Nova license to install seoegypt/value-filter?
- Yes, per the technical evaluation the package has a hard prerequisite of a paid Nova license with valid auth.json credentials. Without that credential, composer require fails with a Nova authentication error that does not mention value-filter, which can misroute debugging. Every CI pipeline that resolves composer.lock inherits the credential requirement. Confirm your Nova major version before attempting integration.
- Is value-filter compatible with Laravel 12, Nova 5, and PHP 8.3+?
- The last release was 2023-05-15, which predates Nova 5, Laravel 12, and PHP 8.3+. The assessment flags three independent break lines: the Nova major with its Vue 2 to Vue 3 tooling shift, the Laravel constraint in composer.json, and the PHP floor. Compatibility is not confirmed, and a stale Composer constraint can block unrelated security upgrades later. Pin an exact tag or copy the code rather than relying on a floating constraint.
- Can I use value-filter to sanitize API input or customer-facing data?
- No, the technical evaluation says it has no role in form requests, jobs, service classes, API input validation, or anything customer-facing. Its realistic fit is internal admin tooling only, for discrete-value equality filtering in an organization that already runs Nova. Using it on revenue-critical or SLA-backed surfaces is explicitly discouraged. Keep customer-facing validation in Laravel's native validation layer.
- What are the production risks of depending on value-filter?
- The assessment lists four risks: staleness and version drift, silent incorrectness where an admin list returns everything, nothing, or the wrong subset with a 200 response, no maintainer, and a description/artifact mismatch that invites misuse. Silent incorrectness is especially dangerous because operators act on the list and no alert fires. Zero dependents means nobody surfaces breakage before you do. Assume abandonment from day one and name an owner for the code.
- Should I install value-filter via Composer or copy the class into my app?
- The pragmatic default in the TPM assessment is to copy the filter class and any Vue component into app/Nova/Filters and resources/js/nova, then delete the Composer dependency. That gives you ownership of roughly fifty lines forever and avoids the Nova credential requirement in CI. Treat the package as a reference implementation or scaffold, not a vendor relationship. The decision is cheap now and expensive to defer.
- Can value-filter handle ranges, operators, tenant scoping, or multi-column filters?
- The evaluation says it fits single-column equality filtering for discrete values like order status, user role, ticket priority, or moderation state. If your requirement needs ranges, operators, tenant scoping, or multi-column logic, it is the wrong tool and the ticket should be rewritten as an in-house filter immediately. Discovering that mid-sprint is the avoidable failure. Confirm the target column is indexed and consider cardinality at millions of rows.
- How do I test value-filter in a Laravel application?
- The context does not provide a test suite or documented test strategy, and the package has zero dependents and no maintainer trail. Write characterization tests against the Nova index query before and after integration, covering empty results, all results, and the expected subset. Verify the apply() behavior against your actual column types and null handling. Because failures are silent 200 responses, assert on the generated query or returned records rather than trusting the UI.
- What are the alternatives to seoegypt/value-filter?
- For admin filtering, an in-house Nova filter class copied into app/Nova/Filters is the main alternative and the recommended ownership model. For input sanitization, use Laravel FormRequest, validation rules, and custom callbacks rather than this package. If you need broader query filtering for APIs, evaluate actively maintained query-builder packages instead. The key question is whether you run Nova at all; if not, the evaluation ends there.
Weaver
How can I help you explore Laravel packages today?