Weave Code
Request Converter Bundle Laravel Package
gepur-it/request-converter-bundle
Symfony bundle from gepur-it that converts incoming HTTP request data into structured, typed objects, helping keep controllers clean and request handling consistent across your application.
Request converter and validator. converts request to DTO
Frequently asked questions about Request Converter Bundle
- Is gepur-it/request-converter-bundle a Laravel package?
- No. It is a Symfony bundle: the -Bundle naming, the symfony/framework-bundle extension class and the DI compiler-pass architecture are Symfony conventions with no equivalent in Laravel's service-provider model. Laravel's router, container and kernel will not consume a bundle manifest, so it cannot be installed and used as a Laravel package.
- Can I use request-converter-bundle in a Laravel application?
- Not without a port. Adopting it in Laravel would mean pulling symfony/http-kernel into the request path, manually registering an event subscriber and rebuilding an argument-resolver/converter chain. That is more bespoke code than writing the request-to-DTO conversion yourself, and it creates a permanent fork-maintenance obligation. The evaluation recommends against attempting the bridge.
- What does gepur-it/request-converter-bundle actually do?
- It converts incoming HTTP request data into structured, typed objects (DTOs) so controllers stay clean and request handling stays consistent. The published description stops there. The repository does not document which inputs it covers (scalars, DTOs, entities, collections), whether it validates or only converts, or how it handles JSON bodies, query strings, uploaded files, nested objects and content negotiation.
- Does request-converter-bundle validate requests, or only convert them?
- The description calls it a request converter and validator, but no documentation confirms what validation it performs, how rules are declared, or how errors are surfaced. Treat validation behaviour as unverified until you read the source. On Laravel, FormRequest and the validation contract already cover this ground natively.
- Which Laravel versions does request-converter-bundle support?
- None. There is no Laravel integration, no service provider and no documented Laravel version constraint because the package targets Symfony. The package's PHP and Symfony version constraints are themselves undocumented, so even on Symfony you must verify them against your lockfile.
- Is request-converter-bundle maintained and safe for production?
- The observable signals are weak: one star, zero dependents, single-org (gepur-it) ownership and no ecosystem validation. The rational default is to treat it as unmaintained until proven otherwise. Before any work, verify the last commit date, open-issue count, CI status, semver tags and Packagist presence.
- How does request-converter-bundle compare to Laravel FormRequest and route model binding?
- They solve the same problem, turning raw request input into typed, validated data, but Laravel's FormRequest, route model binding and validation contract are first-party, documented and maintained. The bundle offers no documented differentiation from those, nor from Symfony's #[MapRequestPayload] / #[MapQueryString] (6.3+) and the older @ParamConverter. That missing differentiation is the central reason the evaluation recommends rejection.
- Is request-converter-bundle a security risk?
- Any package whose job is hydrating objects from raw request data sits directly in the mass-assignment and unsafe-deserialization risk class. With zero dependents, nobody else is finding those defects for you, and there is no vendor or community triage. That combination raises the bar for adoption considerably.
- How do I convert requests to DTOs in Laravel without this package?
- Use FormRequest for validation plus an explicit toDto() or mapper method, or a small dedicated mapper class, and lean on route model binding for identifiers. This keeps controllers clean without a third-party dependency. If you need a stable seam, put the conversion behind an internal RequestDataMapper interface so the implementation can change later.
- Is request-converter-bundle on Packagist and how do I install it?
- The evaluation flags Packagist presence as unverified and notes it may be VCS-only, so confirm distribution before planning anything. Installation is via Composer as a Symfony bundle, which also requires registering the bundle in your Symfony kernel, steps that do not exist in Laravel. In a Laravel app there is no supported install path.
Weaver
How can I help you explore Laravel packages today?