- Is citizen63000/easy-api-bundle compatible with Laravel?
- No. citizen63000/easy-api-bundle is a Symfony bundle built around Symfony routing, Doctrine, Form, Serializer, and dependency injection; the provided README and technical evaluation do not list Laravel support. Laravel developers would need a custom bridge or partial adoption rather than a native install.
- How do I install easy-api-bundle in a Symfony project?
- Install it with Composer using composer require citizen63000/easy-api-bundle, then register the bundle in your Symfony application and add optional easy_api configuration in YAML. The README shows CRUD controllers extending AbstractApiController with CrudControllerTrait and YAML routing using type annotation. This is Symfony setup, not Laravel package discovery.
- Can I use easy-api-bundle CRUD controllers in Laravel?
- You can reuse the CRUD controller pattern only after significant refactoring, because AbstractApiController, Doctrine entities, Symfony forms, and annotation routing do not map directly to Laravel controllers, Eloquent, FormRequest, or Route::apiResource. A service provider or bridge layer would be required for routing, validation, DI, and ORM. Partial adoption, such as borrowing serialization group ideas, is lower risk.
- What Laravel alternatives exist to easy-api-bundle for CRUD APIs?
- For Laravel CRUD APIs, use native make:controller --api, Route::apiResource, API Resources, FormRequest validation, and Eloquent. For OpenAPI documentation, consider darkaonline/l5-swagger or spatie/laravel-api-documentation, and for resource transformations consider spatie/laravel-api-resources or Fractal. These avoid Symfony component dependencies.
- How does easy-api-bundle handle authentication and user tracking?
- The bundle exposes easy_api authentication and user_class settings, plus optional user_tracking with a connection_history_class. These options are Symfony configuration keys and assume Symfony security and Doctrine-style entities. Laravel would need its own auth guard, middleware, and tracking implementation.
- Does easy-api-bundle support OpenAPI or Swagger documentation?
- Yes. It supports Nelmio API-Doc annotations, including OA tags, responses, schemas, and Model references, and it allows self and static constants to be passed as strings in specific annotation cases. In Laravel, l5-swagger is the more natural OpenAPI option.
- How do I configure easy-api-bundle inheritance and form options?
- Configuration is optional YAML under easy_api, covering authentication, user_class, user_tracking, inheritance classes for entity, referential, form, repository, controller, and serialized_form, plus tests debug and datetime_format. Form fields can carry attr options such as group and discriminator or other frontend metadata. These are Symfony config and form concepts, not Laravel config files.
- What are the production risks of using a Symfony bundle in Laravel?
- Main risks include maintaining a Symfony-to-Laravel bridge, synchronizing upstream bundle changes, and carrying Serializer and Form component overhead against Laravel-native tools. Routing, validation, DI, ORM, caching, queues, and testing may need manual integration. Benchmark and scope a documentation-only or inspiration-only adoption before production use.
- How do I test APIs built with easy-api-bundle?
- The bundle provides optional tests settings such as debug and datetime_format, but its test assumptions are Symfony-oriented. In Laravel, test the API with PHPUnit or Pest, feature tests, database factories, and authentication helpers. A bridge layer would need its own integration tests.
- Is easy-api-bundle maintained and does it have a Laravel roadmap?
- The provided context does not publish a roadmap or confirm Laravel support; it describes a Symfony bundle with an unknown long-term Laravel trajectory. Treat upstream maintenance and compatibility as due-diligence items, and prefer Laravel-native packages unless you are willing to own a bridge. Check the GitHub repository for current releases and issues.