Weave Code
Input Http Laravel Package
yiisoft/input-http
Yii HTTP input package for extracting request data from PSR-7 requests, including query parameters, body fields, headers, and uploaded files, with a consistent API for safe access to user input in Yii applications.
Provides Yii Hydrator attributes to get data from PSR-7 HTTP request and adds extra abilities to middlewares processed by Yii Middleware Dispatcher.
Frequently asked questions about Input Http
- Is yiisoft/input-http compatible with Laravel?
- Not directly. It is built for Yii applications and assumes PSR-7 ServerRequestInterface plus Yii Hydrator attributes and Yii Middleware Dispatcher semantics, while Laravel uses Illuminate\Http\Request and Symfony HttpFoundation. You could bridge it, but it would sit beside Laravel rather than integrate natively.
- Can I use yiisoft/input-http in a Laravel application?
- Only with a custom adapter. You would need to convert Laravel requests to PSR-7, invoke the Yii hydrator, and translate results or failures back into Laravel responses. That adapter adds a narrow, high-maintenance boundary and offers limited value over Laravel request injection and FormRequest validation.
- How do I install yiisoft/input-http for Laravel?
- There is no Laravel-specific installation path. Composer can install yiisoft/input-http, but you must also satisfy Yii Hydrator, PSR-7 implementation, and possibly Yii Middleware Dispatcher constraints. For Laravel, native request handling and FormRequest require no such glue.
- Does yiisoft/input-http support Laravel versions such as 10 or 11?
- The package does not target Laravel versions at all. Its compatibility should be checked against PHP, PSR-7 implementations, Yii Hydrator, and Yii Middleware Dispatcher, not Laravel's release cycle. Because the repository is unknown and has a single visible 2024 release, verify support from source and CI rather than assuming Laravel 10 or 11 compatibility.
- Does yiisoft/input-http work with Laravel FormRequest validation?
- No. It provides structured input extraction from PSR-7 requests, not Laravel validation. FormRequest, validators, and Laravel middleware operate on Illuminate\Http\Request, so you would need to translate between the two systems. Native FormRequest is simpler and better supported.
- How does yiisoft/input-http compare to Laravel's Request and FormRequest?
- It solves a different problem in a different ecosystem. yiisoft/input-http hydrates DTOs from PSR-7 requests using Yii attributes, while Laravel's Request and FormRequest provide request access, validation, authorization, and middleware integration. For Laravel, native tools cover the use case with less risk and no adapter.
- Is yiisoft/input-http safe for production Laravel apps?
- Treat it as high risk relative to value. The package has 11 stars, an unknown repository, a single visible release dated 2024-08-06, and tight coupling to Yii components, so API stability, dependency compatibility, security review, and maintainer availability all need scrutiny. It should not be a core Laravel dependency without a strong Yii-related reason.
- What are alternatives to yiisoft/input-http for Laravel?
- Use Laravel's native Request injection, FormRequest validation, middleware, and DTO mapping. If you need PSR-7 at an architectural boundary, choose a maintained PSR-7 bridge and map to Laravel requests explicitly. For attribute-driven DTO hydration, Laravel-friendly packages and custom data objects are lower-risk than adopting Yii-specific components.
- When would yiisoft/input-http make sense in a mixed PHP estate?
- It can make sense if your organization already runs Yii services and needs PSR-7 request-to-DTO hydration inside Yii middleware. In that case, keep it isolated behind an internal interface and pin versions. For a Laravel application, it is better as a design reference than a dependency.
- How should I test a yiisoft/input-http adapter in Laravel?
- Build contract tests around the adapter boundary: Laravel request to PSR-7 conversion, hydration output, validation or error translation, and file upload handling. Keep the adapter behind an internal interface so you can replace it with native Laravel request mapping. Also add dependency and security checks because the upstream repository is not well known.
Weaver
How can I help you explore Laravel packages today?