Weave Code
Simple Rest Crud Bundle Laravel Package
hessnatur/simple-rest-crud-bundle
A Symfony bundle that adds simple RESTful CRUD capabilities to your application, helping you scaffold create, read, update, and delete endpoints with minimal configuration. Lightweight and straightforward for basic resource management.
Classes, interfaces and controllers to build a simple crud api with symfony framework.
Frequently asked questions about Simple Rest Crud Bundle
- Is hessnatur/simple-rest-crud-bundle a Laravel package?
- No. It is a Symfony 4 bundle that scaffolds REST CRUD endpoints using abstract classes and services built around FOSRestBundle, JMS Serializer, and LexikFormFilterBundle. It assumes a Symfony kernel, bundle registration, and Symfony service-container conventions. It is not a Laravel package and should not be treated as one.
- Can I install hessnatur/simple-rest-crud-bundle in a Laravel app with Composer?
- Composer may install the dependency, but the code will not work as a Laravel package. The bundle's DependencyInjection extension, service definitions, and base classes expect Symfony's kernel and bundle registration model. Laravel's container, HTTP kernel, and routing are structurally different, and no adapter layer is provided. Do not plan on composer require in a Laravel application.
- What does hessnatur/simple-rest-crud-bundle actually provide?
- It provides classes, interfaces, and controllers intended to scaffold create, read, update, and delete API endpoints in Symfony. The design is oriented around inheritance from abstract base classes, with services handling routing, serialization, validation, filtering, and pagination assumptions. It is a thin internal-abstraction layer over FOSRestBundle, JMS Serializer, and LexikFormFilterBundle rather than a full framework.
- What are Laravel and Symfony alternatives to this CRUD bundle?
- In Laravel, the first-class equivalents are Eloquent API Resources, FormRequest validation, resource controllers, spatie/laravel-query-builder for filtering and pagination, and laravel/sanctum for API authentication. In Symfony, API Platform is the actively maintained choice for REST CRUD with serialization, validation, and filtering. These alternatives are maintained and integrate natively with their respective frameworks.
- Does hessnatur/simple-rest-crud-bundle support Laravel 10 or Laravel 11?
- No. The bundle targets Symfony 4, which reached end of life with Symfony 4.4 in November 2023. There is no Laravel version support, and there is no evidence of compatibility with Laravel 10, Laravel 11, or newer Laravel releases. Using it in a modern Laravel app would require porting Symfony-specific conventions.
- Is hessnatur/simple-rest-crud-bundle actively maintained?
- The maintenance signals are weak: 1 star, 0 dependents, no visible roadmap, and no evidence of issue triage or downstream usage. It appears to be a public mirror of one company's internal scaffolding rather than a community-maintained package. Treat it as code you must review entirely rather than a trust-by-default dependency.
- What are the production risks of using this bundle?
- The main risks are abandonment, end-of-life Symfony 4 and PHP runtime constraints, inheritance coupling through abstract base classes into your domain model, and low supply-chain scrutiny due to near-zero usage. It also leans on three third-party bundles with their own version constraints and deprecation timelines, including FOSRestBundle in maintenance mode. Those factors make it a high-risk dependency for production use.
- How would I configure hessnatur/simple-rest-crud-bundle in a Symfony application?
- You would register the bundle in the Symfony kernel, extend its abstract CRUD controller and service classes, and wire FOSRestBundle, JMS Serializer, and LexikFormFilterBundle according to their version constraints. You would also need to pin the Symfony major version the bundle targets and verify PHP version floors. Even in Symfony, API Platform is usually the more defensible foundation for the same problem.
- How do I test a Symfony app that uses hessnatur/simple-rest-crud-bundle?
- Testing requires a Symfony test kernel plus working configuration for FOSRestBundle, JMS Serializer, and LexikFormFilterBundle. Because the bundle relies on abstract base classes, your tests must also accommodate its inheritance and service-container conventions, which makes mocking and refactoring harder. In a Laravel context, HTTP feature tests around native resource controllers and FormRequests are the simpler path.
- Should I use hessnatur/simple-rest-crud-bundle as a dependency or as a reference implementation?
- Treat it as a reference implementation, not a dependency. Its realistic value is architectural: the abstract classes show an opinion about decomposing list, filter, read, create, update, and delete endpoints and where serialization, validation, and filtering belong. Read the source, extract the patterns you agree with, and reimplement them idiomatically in Laravel or Symfony. That costs review time but carries zero dependency risk.
Weaver
How can I help you explore Laravel packages today?