- Can I use osm/easy-rest-bundle in a Laravel application?
- No. osm/easy-rest-bundle is a Symfony bundle, not a Laravel package, and it is structurally coupled to Symfony's HttpKernel, dependency injection container, event dispatcher, and routing conventions. Laravel uses a different container and middleware pipeline, and there is no adapter or bridge package. In a Laravel codebase it should be rejected at intake for framework mismatch.
- How do I install osm/easy-rest-bundle?
- Installation would be through Composer into a Symfony application, followed by registering the bundle in the Symfony kernel and configuring it there. There is no Laravel package discovery or service provider, so composer require in Laravel will not make it work. Before installing, audit its composer.json constraints against your PHP and Symfony baseline because the published constraints are likely outdated.
- Which Symfony and PHP versions does osm/easy-rest-bundle support?
- The repository does not document supported Symfony or PHP versions. Given its vintage and single-maintainer status, it most likely pins Symfony 2.x or 3.x-era constraints and predates PHP 8 and Symfony 6/7. Treat compatibility with any current baseline as unverified until you run a composer.json audit and test a fork.
- What does osm/easy-rest-bundle do?
- It is a Symfony bundle intended to streamline REST API development by exposing Doctrine entities as JSON endpoints. Its stated features include automatic CRUD routing, pagination, filtering, and serialization with minimal configuration. The documented scope is limited, so the source code is effectively the specification.
- Does osm/easy-rest-bundle generate CRUD routes for Doctrine entities?
- Yes, automatic CRUD routing for Doctrine entities is the bundle's headline feature according to its description. It aims to provide convention-based endpoints with little configuration. However, the exact routing behavior, error semantics, and customization points are not documented and would need to be verified in the source.
- How does pagination and filtering work in osm/easy-rest-bundle?
- Pagination and filtering are advertised features, presumably applied to entity collections exposed through the generated REST routes. The bundle description does not specify query parameter names, defaults, or extension points. You would need to inspect the code and write characterization tests before relying on the behavior.
- Does osm/easy-rest-bundle handle JSON serialization and content negotiation?
- The description promises configurable serialization and content negotiation for JSON responses. It does not document which serializers are supported, how normalization groups work, or how content negotiation is negotiated. Those details are in the code, which shifts discovery and validation cost to the adopting team.
- Is osm/easy-rest-bundle actively maintained and safe for production?
- The adoption signals are weak: roughly 9 stars, zero dependents, and a single maintainer with no visible release cadence. Zero public dependents means no production system has validated the bundle under real load. There is no security advisory process or SLA, so production use would transfer all ongoing risk to your team.
- What are better alternatives to osm/easy-rest-bundle for REST APIs?
- In Laravel, use native API Resources, Form Requests, route-model binding, and Sanctum or throttling rather than a Symfony bundle. In Symfony, evaluate API Platform with the Symfony Serializer, which is actively maintained and documents serialization, pagination, filtering, and content negotiation. Both are stronger fits than an unmaintained bundle with no dependents.
- Can osm/easy-rest-bundle be ported or migrated to Laravel?
- There is no migration path because the boundary is a framework boundary, not an adapter boundary. The realistic options are running a separate Symfony runtime, which adds a second framework lifecycle, or vendoring the MIT-licensed source as a design reference and rewriting the behaviors natively in Laravel. Neither is an integration of the package.