Weave Code
Json Request Bundle Laravel Package
filament-uno/json-request-bundle
Simplify JSON request handling in Laravel and Filament with a ready-made request bundle. Standardize validation, parsing, and structured responses so your app's JSON APIs and Filament workflows stay consistent, maintainable, and easy to extend.
Symfony JsonRequest Bundle
Frequently asked questions about Json Request Bundle
- What is filament-uno/json-request-bundle used for?
- It is a republished bundle aimed at standardizing JSON request handling in Laravel and Filament applications, covering request parsing, validation helpers, centralized error handling, and structured JSON responses. The stated goal is to reduce controller boilerplate and keep JSON-driven endpoints consistent and easy to extend. In practice its code originates from the archived SymfonyBundles JsonRequest bundle at commit fa0e3d2, so the feature set reflects Symfony bundle conventions rather than Laravel-native patterns.
- Is filament-uno/json-request-bundle a Laravel package or a Symfony bundle?
- The v1.0.0 release explicitly says it is based on the original SymfonyBundles JsonRequest bundle at commit fa0e3d2, which indicates a republish of an archived Symfony bundle rather than a Laravel-native rewrite. The technical evaluation found no evidence of a rename off the -bundle convention, a Laravel service provider, or a changed platform constraint. Treat it as a Symfony bundle snapshot re-tagged for Composer consumption, not as a successor to the archived upstream.
- Which Laravel and PHP versions does filament-uno/json-request-bundle support?
- No explicit compatibility statement appears in the release note, and a snapshot of a 2020 commit inherits that era's constraint set. Laravel 10 and 11 require PHP 8.1 and 8.2 respectively, so without a declared platform constraint you should expect composer install to refuse, and --ignore-platform-reqs is not an acceptable production workaround. Verify the declared PHP requirement and the symfony/http-kernel constraint in composer.json before attempting adoption.
- How do I install filament-uno/json-request-bundle with Composer?
- The conventional command is composer require filament-uno/json-request-bundle, but installation is exactly where the supply-chain and platform risks surface. Confirm the vendor namespace is genuine and check whether the package replaces or conflicts with the original Symfony bundle. Before running anything, diff the v1.0.0 tag against commit fa0e3d2, since an hour of comparison tells you whether this is a pure republish or contains real work.
- Does filament-uno/json-request-bundle replace Laravel FormRequest and validated()?
- No, it does not replace them, and the evaluation warns that adopting it risks running a parallel validation stack alongside Laravel's native tooling. If symfony/validator remains a hard dependency, you end up with two rule languages and two error formats in one application, which is a real maintenance and consistency hazard. FormRequest with $request->validated() remains the idiomatic path for JSON validation in Laravel.
- Is filament-uno/json-request-bundle safe for production?
- The 1.0.0 tag is a stability claim asserted on a frozen snapshot with no changelog, no diff summary, and no stated maintenance intent, so the semver number communicates more confidence than has been demonstrated. The upstream was archived with no security patching for more than four years, and there is no visible issue tracker activity, release cadence, CI matrix, or second contributor. For code that executes on every request, that combination is a serious production concern.
- How should I test JSON validation with filament-uno/json-request-bundle?
- The release ships no documented CI matrix or test suite you can rely on, so plan to write your own feature tests that exercise each JSON endpoint end to end. Assert response shape and status codes explicitly, because the package's centralized error handling may alter Laravel's default error formats. If testability is a priority, compare against FormRequest-based validation, which integrates directly with Laravel's HTTP testing helpers.
- What are the best alternatives for handling JSON requests in Laravel?
- FormRequest with validated() is the native choice and covers most validation and parsing needs without extra dependencies. Spatie's laravel-data is a strong option when you want typed data objects and structured transformation, and a plain Validator call works well for small focused endpoints. All three avoid the parallel-validation and abandoned-upstream risks this bundle carries.
- Is filament-uno/json-request-bundle actively maintained?
- There is no evidence of active maintenance: the v1.0.0 release re-tags an archived 2020 commit, and no changelog, release cadence, issue tracker activity, or second contributor is visible. A new tag restarts the release clock but not the maintenance itself. The question of who patches a transitive dependency CVE now has a name attached, which is not the same as an answer.
- What should I verify before adopting filament-uno/json-request-bundle?
- First, diff the v1.0.0 tag against commit fa0e3d2 to determine whether anything changed beyond the version number. Then inspect composer.json for the declared PHP constraint and whether symfony/http-kernel and symfony/validator remain hard dependencies. Finally, confirm who publishes the vendor namespace, whether it is a genuine transfer or a lookalike, and whether the package renames or replaces the original. If none of that produces a clear answer, the safer path is FormRequest or laravel-data.
Weaver
How can I help you explore Laravel packages today?