Weave Code
Resource Bundle Laravel Package
sylius/resource-bundle
SyliusResourceBundle provides format-agnostic CRUD controllers and persistence utilities for Symfony apps, built on Doctrine's ObjectManager and ObjectRepository interfaces. It simplifies listing, filtering, sorting, and displaying resources without duplicating controllers.
Simpler CRUD for Symfony applications
Frequently asked questions about Resource Bundle
- Can I use sylius/resource-bundle in a Laravel application?
- No. sylius/resource-bundle is a Symfony bundle wired through Symfony's HttpKernel, DependencyInjection, Routing, EventDispatcher, Form, and DoctrineBundle, and it ships no Laravel service provider, facade, or publishable config. Laravel's Eloquent ORM does not implement Doctrine's ObjectManager/ObjectRepository contracts, so direct in-process adoption would require running Doctrine alongside Eloquent with duplicated migrations and two unit-of-work lifecycles. The realistic option is a separate Symfony service that exposes CRUD endpoints for Laravel to consume over HTTP.
- Does SyliusResourceBundle work with Eloquent?
- No, it relies on Doctrine Common Persistence interfaces, mainly ObjectManager and ObjectRepository. Eloquent is an ActiveRecord implementation and does not satisfy those contracts. Bridging the two would mean maintaining Doctrine and Eloquent side by side, which is a high-risk dual-ORM design rather than a supported integration.
- How do I install sylius/resource-bundle in Laravel or Symfony?
- In Symfony, install it with Composer and register the bundle in your Symfony kernel; there is no config/resource.php to publish and no Laravel package discovery. In Laravel, do not install it into the Laravel composer.json because there is no service provider, facade, or Eloquent integration. The only sensible path is a separate Symfony service.
- What Laravel, PHP, and Symfony versions does sylius/resource-bundle support?
- There are no Laravel versions to support because this is not a Laravel package. The 1.11 line requires PHP 8.1+ and supports Symfony 5.4, 6.x, and 7.x, with Doctrine ORM or ODM. Optional integrations include JMS Serializer ^5.0, Pagerfanta ^4.0, Twig, and Symfony Workflow.
- What does sylius/resource-bundle actually do?
- It provides format-agnostic CRUD controllers, resource metadata via the AsResource PHP attribute, routing factories, and basic sorting, filtering, and pagination on top of Doctrine's ObjectManager and ObjectRepository interfaces. It is the CRUD substrate Sylius itself is built on and is designed to remove duplicated controller code for listing, filtering, sorting, and displaying resources. It is explicitly not an admin generator and does not create forms, grids, or filters for you.
- Is SyliusResourceBundle an admin generator?
- No. The README is explicit that it will not create forms, filters, or grids for you. It only gives you format-agnostic controllers and basic sorting/filter mechanisms as a foundation to build on. If you need a full admin panel generator, this package is not that tool.
- How do I add filtering, sorting, and pagination with SyliusResourceBundle?
- You define resources with the AsResource attribute and use the bundle's routing factories and CRUD controllers, then configure basic sorting and filter mechanisms on top of Doctrine repositories. Pagination is typically handled with Pagerfanta, which the bundle allows at ^4.0. Filter allow-listing and N+1 tuning remain your responsibility, so review queries before production.
- Can I run sylius/resource-bundle as a separate Symfony service for a Laravel app?
- Yes, that is the only realistic integration path. Run a bounded-context Symfony service with Doctrine, expose CRUD endpoints, and let the Laravel app consume them over HTTP. Budget for operating a second framework runtime, including deployment, security patching, and Symfony/Doctrine fluency on the team; a one-to-two-week spike with one resource, attribute routing, JSON responses, pagination, and one filter is a sensible first step.
- Which branch of sylius/resource-bundle should I use in production?
- There is no main or master branch. The 1.10 line is for bug fixes and improvements to existing features, while 1.11 is for new features and bigger changes, including namespace relocations that can cause minor-version BC breaks. Pin to 1.10 if you need stability, or to a specific 1.11 release if you need the newer features and can absorb the churn.
- What are good alternatives to sylius/resource-bundle for Laravel CRUD?
- For Laravel-native CRUD, use Laravel resource controllers, API Resources, Eloquent, and packages such as Laravel Nova, Filament, or Backpack for admin panels. Those stay inside Laravel's service container, ORM, and routing conventions and avoid a second framework runtime. Choose sylius/resource-bundle only when the target application is Symfony and Doctrine-based.
Weaver
How can I help you explore Laravel packages today?