- Is oxidmod/rest-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package, even though it is frequently listed alongside Laravel and general PHP packages. The package overview explicitly describes it as a Symfony bundle based on the Fractal library, offering reusable controllers, serialization helpers and request handling utilities. If you are looking for a drop-in Laravel API package, this is not one, so confirm the integration surface in the repository before planning around it.
- How do I install oxidmod/rest-bundle with Composer?
- Install it with composer require oxidmod/rest-bundle, then register the bundle in your Symfony application's bundle configuration. Because the package is still on a 0.2.x version, pin an exact or tilde constraint such as 0.2.4 rather than a caret constraint. Diff the require block in composer.json before installing so you know exactly which production dependencies you are inheriting.
- What does oxidmod/rest-bundle actually do, and what is its public API surface?
- It is a thin layer over the Fractal library that aims to reduce boilerplate when exposing JSON REST endpoints in Symfony. The described feature set is reusable controllers, serialization helpers and request handling utilities for consistent responses. The specific namespaces, base controller classes and extension points are not documented in the available README excerpt, so read the source and composer.json before committing to a design.
- Which PHP and Symfony versions does oxidmod/rest-bundle support?
- The supported PHP floor and Symfony version range are not documented in the material available and must be read directly from the require block in composer.json. Do not trust a directory listing or a support badge, since those go stale quickly on pre-1.0 packages. Check the constraints against your own PHP and Symfony versions before upgrading or adopting.
- Can I use oxidmod/rest-bundle in a Laravel application?
- Not directly, because Laravel has no bundle registration system, so a Symfony bundle would need manual service wiring or a custom adapter. Nothing in the package description suggests Laravel service provider, facade or config publishing support. For Laravel projects, evaluate native API Resources or a dedicated Fractal wrapper such as spatie/laravel-fractal instead.
- What changed in oxidmod/rest-bundle 0.2.4 and is it safe to upgrade?
- The only stated change is the addition of mutation testing to the package's development and CI pipeline, with no indicated runtime features, deprecations or API changes. The practical risk from a patch like this is packaging hygiene, so verify that the mutation testing tool sits in require-dev and that the php constraint did not shift upward. If that two-minute check is clean, 0.2.3 to 0.2.4 should require no application code changes.
- Should I use a caret constraint like ^0.2 for oxidmod/rest-bundle?
- No, avoid caret constraints on pre-1.0 packages. Under semantic versioning, every 0.x minor release is permitted to introduce breaking changes, so ^0.2.4 could silently pull in a 0.3.0 that breaks your integration. Pin an exact version or a tilde constraint and bump deliberately, running your test suite against each new release.
- Do I need to know the Fractal library to use oxidmod/rest-bundle?
- Yes, practically speaking. The bundle is a convenience layer over Fractal, so transformers, serializers and includes behave the way Fractal defines them rather than introducing a new abstraction. Learning Fractal's transformer and serializer concepts first makes the bundle's helpers obvious and keeps you from fighting the underlying library.
- Is oxidmod/rest-bundle production ready and well maintained?
- Treat it as pre-1.0 software: the 0.2.x version number conveys no API stability guarantee, and there is no published backward compatibility policy in the available material. The recent addition of mutation testing to CI is a positive maintainer-quality signal, but it says nothing about runtime stability or documentation depth. Assess the repository's commit cadence, test coverage and issue responsiveness before making it a production dependency.
- What are the alternatives to oxidmod/rest-bundle for building REST APIs?
- You can use the underlying league/fractal library directly and skip the bundle wrapper entirely, which removes one layer of pre-1.0 risk. On Symfony, API Platform and the Symfony Serializer component cover the same ground with far larger communities and documented support matrices. On Laravel, native API Resources or spatie/laravel-fractal are the conventional choices.