- What is olegkunitsyn/json-rpc-bundle used for?
- It is a Symfony bundle implementing JSON-RPC 2.0 services, with request and response handling, method routing, structured error objects, and HTTP kernel and service container integration. It is aimed at exposing PHP application APIs to remote JSON-RPC clients. It is not a Laravel package.
- Can I use olegkunitsyn/json-rpc-bundle in a Laravel application?
- It is built as a Symfony bundle, so it expects Symfony's HTTP kernel and service container rather than Laravel's service providers, facades, and routing. There is no documented Laravel service provider or config publish step in the available material. Laravel teams should treat it as a Symfony-native package and validate a custom integration or prefer a Laravel-native JSON-RPC package.
- How do I install olegkunitsyn/json-rpc-bundle?
- It is a Composer package, so you add it with Composer and register the bundle in a Symfony application's bundle configuration. The available release note does not include exact package metadata or an install guide, so check the repository README and composer.json for the current constraint. For Laravel, installation alone does not provide framework integration.
- What changed in version 7.0.1?
- The only available release note says 7.0.1 supports batches, DTOs, and response normalization. There is no published 7.0.0 changelog in the provided material. Because 7.0.1 is a patch on a new major, treat the 7.x line as immature until a 7.0.x release cadence and upgrade guide are visible.
- Does this package support JSON-RPC batches?
- Version 7.0.1 is noted as supporting batches, which implies bulk request handling. The available material does not state whether batch execution is synchronous, queue-backed, or both. It also does not define partial-failure semantics, payload limits, or whether results are per-item or all-or-nothing, so verify these before relying on batching in production.
- What are the DTOs in json-rpc-bundle 7.x?
- The 7.0.1 note mentions DTOs, implying a typed data-transfer layer between the package and application code. It is not stated whether DTOs are mandatory at all boundaries or opt-in via configuration. A mandatory DTO layer would force refactoring at every call site, so test a representative slice before upgrading.
- What does response normalization mean for existing clients?
- Response normalization suggests the package emits a single response envelope, which can be good for controllers and API resources but is a contract change for consumers. Mobile clients, partner integrations, stored fixtures, and contract tests that read raw responses may break silently. Enumerate every downstream consumer and version public response shapes before adopting 7.x.
- Which Laravel and PHP versions are supported?
- The available material does not list PHP or Laravel version floors; in fact, the package is a Symfony bundle rather than a Laravel package. Check composer.json for PHP and Symfony constraints and verify them against your application before design work. Do not assume Laravel version support from the package name or release note.
- Is json-rpc-bundle production-ready for a critical API?
- Treat 7.x as high risk until a 7.0.x cadence, changelog, and upgrade guide are available. The lack of a documented 7.0.0 changelog and the quick 7.0.1 patch are weak signals. For critical paths, pin to the last 6.x release, record behavior as a baseline, and run a spike against 7.0.1 with batch and failure cases.
- What are alternatives for JSON-RPC in Laravel?
- If you need Laravel-native integration, evaluate Laravel JSON-RPC packages or build a thin JSON-RPC layer on Laravel routes, controllers, and validation. This Symfony bundle can still be studied for JSON-RPC 2.0 error shapes and routing ideas. Compare maintenance activity, Laravel version support, batch semantics, and response contract stability before choosing.