Weave Code
Rest Client Sdk Bundle Laravel Package
mapado/rest-client-sdk-bundle
Symfony bundle that integrates the Mapado REST Client SDK, registering API client services and configuration in the container so Symfony apps can inject and use Mapado REST clients with less boilerplate.
Symfony Bundle for https://github.com/mapado/rest-client-sdk
Frequently asked questions about Rest Client Sdk Bundle
- Can I use mapado/rest-client-sdk-bundle in a Laravel application?
- No. It is a Symfony bundle booted by the Symfony Kernel, and Laravel's package discovery will not register it. For Laravel, use the framework-agnostic mapado/rest-client-sdk directly and write your own container bindings.
- What does mapado/rest-client-sdk-bundle actually do?
- It integrates the Mapado REST Client SDK into Symfony by registering configured API clients as container services. That centralizes endpoints, credentials, and client options and enables autowiring in Symfony services. The bundle is mostly DI glue; the underlying SDK does the HTTP and serialization work.
- Does mapado/rest-client-sdk-bundle support Laravel 10 or Laravel 11?
- No, there is no Laravel support. The package targets Symfony and does not ship a Laravel service provider or facade. Its Composer constraints are from the Symfony 3.x/4.x era, so it may not resolve cleanly on modern PHP and Laravel stacks.
- How do I integrate the Mapado REST Client SDK into Laravel without the bundle?
- Install only mapado/rest-client-sdk, then bind its client and entity manager as Laravel singletons in a service provider. Load endpoint and credential config from config/services.php or a dedicated config file. Wrap the SDK in a gateway interface so controllers and jobs depend on your abstraction, not SDK types.
- Is mapado/rest-client-sdk-bundle maintained and safe for production?
- The assessment flags abandonment risk: four stars, zero dependents, and no visible maintenance cadence. That means little downstream battle-testing and uncertain security responsiveness. Treat the bundle as a reference implementation, not a dependency you rely on for production.
- What are the alternatives to using this bundle in Laravel?
- Use the underlying mapado/rest-client-sdk behind a hand-written gateway, or generate a client from the vendor's JSON descriptor with a tool like Jane PHP. You can also use Symfony HttpClient or Laravel's HTTP client directly for simple APIs. The bundle adds no capability beyond the SDK, so its convenience is easy to replace.
- What versions of PHP and Symfony does mapado/rest-client-sdk-bundle require?
- The bundle is from the Symfony 3.x/4.x era, so expect stale Composer constraints and transitive pins on JMS Serializer and Guzzle. Validate against your PHP 8.2+ runtime before planning any work. In most cases you will need to loosen constraints or vendor a fork you control.
- How much work is it to replace the bundle's wiring in Laravel?
- The assessment estimates roughly 100 lines of container wiring for a basic integration. You bind the SDK client and entity manager as singletons, load config, and expose a repository-per-resource API. That is a days-to-one-sprint effort, not a multi-quarter program.
- Should I use this bundle if I only have a few API endpoints?
- Probably not. Below three or four endpoint families, the boilerplate savings never compound, and hand-written clients with contract tests are cheaper. The bundle's value is convenience in Symfony autowiring, which Laravel does not get anyway.
- How should I test a Laravel integration with the Mapado REST Client SDK?
- Generate or write clients at build time, then prove serialization against a sandbox before production. Add contract tests for request shapes, response mapping, and error translation at your gateway boundary. Pin a fork you control and re-run the generation pipeline on every PHP or Laravel upgrade.
Weaver
How can I help you explore Laravel packages today?