Weave Code
Request Validator Bundle Laravel Package
gepur-it/request-validator-bundle
A Symfony bundle that validates incoming request data against declarative rules, with clean error responses and easy integration into controllers.
Request Valitator for symfony
Frequently asked questions about Request Validator Bundle
- Is gepur-it/request-validator-bundle compatible with Laravel?
- No. It is a Symfony bundle built around HttpKernel, EventDispatcher, and DependencyInjection compiler passes, and it registers through Kernel::registerBundles() plus config/bundles.php, none of which exist in Laravel. Laravel has no execution path for its service wiring, extension class, or kernel-boot assumptions. Treat it as Symfony-only and use Laravel's Validator or FormRequest for the same job.
- Can I install gepur-it/request-validator-bundle with Composer in a Laravel app?
- You can add it to composer.json, but installing it will not make it work. The package ships no Laravel service provider, no middleware, and no config integration, so nothing in Laravel's request pipeline will ever call it. It also risks dependency conflicts because its Symfony and PHP version constraints are not clearly declared. The recommended answer is to reject the dependency.
- Which Laravel versions does request-validator-bundle support?
- None are declared. The package targets symfony/* components rather than illuminate/* components, so there is no supported Laravel version matrix today. Any Laravel compatibility would be something you build yourself through a port, not something you get from the package.
- How should I validate incoming request data in Laravel instead?
- Use Laravel's native Validator, FormRequest, or a middleware that invokes the validator. FormRequest already gives you declarative rules, authorization gating, and structured 422 error responses, which covers the use case this bundle appears to target. If you want the bundle's specific conventions, reimplement them as a base FormRequest or a thin middleware rather than importing the code.
- What does gepur-it/request-validator-bundle do that Laravel FormRequest does not?
- Based on the available information, nothing that justifies the integration cost. The bundle validates inbound request data against declarative rules and returns clean error responses, which is exactly what FormRequest and the Validator component already do in Laravel. The only potential value is its specific conventions, such as a particular error envelope or per-route validator resolution, and those can be copied without the dependency.
- How would I port request-validator-bundle rules into a Laravel project?
- Timebox a short spike, read the source end to end, and document the exact validation semantics it enforces. Produce a one-page diff against FormRequest behaviour, then reimplement only the parts you actually want as a BaseFormRequest plus optional middleware, typically around 100 to 300 lines. Keep the MIT attribution in a header comment if you copy any code.
- Is gepur-it/request-validator-bundle actively maintained and production-ready?
- The maturity signals are weak: one star, zero dependents, a composite score around 0.005, and no visible CI or release cadence. There is no evidence of a security disclosure process, no test coverage signal, and it is effectively a single-maintainer project. For a validation component that sits on a trust boundary in front of every write path, that is the wrong risk profile.
- Does request-validator-bundle have a test suite and CI that I can trust?
- There is no evidence of CI or meaningful test coverage in the repository signals reviewed here. For a validation layer that guards every write path, untested rule evaluation is a blocker rather than a nice-to-have. If you port the conventions into Laravel, write your own feature tests covering valid payloads, invalid payloads, and each error response shape.
- Does request-validator-bundle validate query strings and headers, and how are validation failures returned?
- That is not documented in the available information and would need to be confirmed by reading the source. It is unclear whether the bundle validates only the request body or also query parameters, headers, and route params, and whether it coerces between JSON and form content types. The exception type, HTTP status, and response body shape for failures are likewise open questions that must be answered before copying any convention.
- What are the best alternatives to request-validator-bundle for a Laravel application?
- Laravel's built-in Validator, FormRequest, and middleware cover the same ground with full framework support, documentation, and a mature testing story. If you need RFC 7807 problem-details responses or a per-endpoint validator registry, those are small conventions you can implement in a base FormRequest or your own small package. There is no Laravel-native fork of this bundle referenced in the material reviewed.
Weaver
How can I help you explore Laravel packages today?