Weave Code
Sylius Easy Crud Plugin Laravel Package
agence-adeliom/sylius-easy-crud-plugin
Sylius Easy CRUD Plugin streamlines building admin CRUD interfaces in Sylius. Quickly generate grids, forms and controllers with minimal boilerplate, speeding up plugin and store development while staying consistent with Sylius conventions.
At a glance
Frequently asked questions about Sylius Easy Crud Plugin
- What does the Sylius Easy CRUD Plugin actually do?
- It is a Composer package that streamlines building create, read, update and delete screens in the Sylius admin panel. It provides a reusable CRUD controller plus resource helpers, so you spend less time wiring controllers, grids, forms and routing by hand. Everything follows Sylius conventions, so it plugs into the existing admin architecture rather than replacing it. It is aimed at store developers and plugin authors who build many admin resources.
- Is this package for Laravel or for Sylius and Symfony?
- It targets Sylius, which is built on Symfony, not Laravel. The Composer install workflow will feel familiar, but you register it as a Symfony bundle inside a Sylius application rather than as a Laravel service provider. If you are a Laravel developer moving into Sylius, expect Symfony concepts such as bundles, services and YAML or PHP routing configuration.
- How do I install agence-adeliom/sylius-easy-crud-plugin with Composer?
- Run composer require agence-adeliom/sylius-easy-crud-plugin in the root of your Sylius application. Then enable the bundle in config/bundles.php so Sylius loads its services and configuration. After that you can start defining admin resources that use the provided CRUD controller. Check the repository README for the exact bundle class name and any extra setup steps.
- How does the reusable CRUD controller reduce boilerplate?
- It gives you a base controller that already handles the standard index, show, create, update and delete flows. Instead of duplicating that logic for every admin resource, you extend or configure the controller and point it at your resource, grid and form. That keeps your code shorter and more consistent with the rest of the Sylius admin. Custom actions can still be added on top when a resource needs something special.
- How do I configure the grid and form for a new admin resource?
- You define a grid with columns, filters and actions, and a form type, exactly as you normally would in Sylius. Then you reference them from your resource configuration and controller. The convention-based defaults cut down the amount of explicit wiring you need. Existing Sylius grid and form documentation still applies, so your usual configuration patterns carry over.
- How does admin routing work with this plugin?
- Admin routes are typically declared using the standard Sylius resource routing, with the plugin's helpers trimming the repeated route blocks. Because the package stays inside Sylius conventions, the routes show up in the admin just like core resources. You can still add or override individual routes when you need custom actions or URLs. Route names follow the usual Sylius prefixing, so existing menu and grid action links keep working.
- Can I use it inside my own custom Sylius plugin?
- Yes, it works in any Sylius application, including reusable plugins you distribute through Composer. You register the bundle in your plugin's dependency setup and define resources the same way you would in an application. This makes it especially useful for agencies maintaining several Sylius plugins that each ship an admin panel. Just declare the dependency in your own composer.json so consumers get it automatically.
- Which Sylius and PHP versions are supported?
- Support depends on the release you install, so check the composer.json constraints and the repository README for exact Sylius and PHP versions. As a rule, pick the plugin version that matches your Sylius minor release. If you are on an older Sylius branch, verify compatibility before upgrading your application. Running Composer's dependency resolution in a test branch first is the safest way to confirm.
- How should I test a CRUD resource built with this plugin?
- Test it like any Sylius admin feature, using functional tests that hit the admin routes and assert grid listing, form submission and persistence. Because the controller is reusable, a single test pattern can cover many resources. Seed data with fixtures or Foundry factories and run the suite in CI against the Sylius version you deploy. Add a smoke test for each new resource so routing or form configuration regressions surface early.
- Is it production-ready and how does it compare to alternatives?
- It is a small, convention-focused helper rather than a full admin generator, so production suitability mostly depends on your own configuration and test coverage. Review the repository's release history and issue tracker to judge maintenance activity before committing to it. Alternatives include hand-writing Sylius CRUD resources or adopting broader admin-generation tooling. The plugin is a good fit when you want minimal boilerplate while staying close to Sylius core conventions.
Weaver
How can I help you explore Laravel packages today?