Weave Code
Crud Bundle Laravel Package
symkit/crud-bundle
symkit/crud-bundle is a Symfony bundle that streamlines CRUD development with reusable scaffolding for create, read, update, and delete workflows. It reduces boilerplate for admin panels and data-management screens, helping teams build consistent list, form, and detail views faster.
Symfony bundle for modern applications: generic CRUD, Live lists (filters, sort, pagination), Twig components (BackLink, DeleteForm, CrudList, CrudFilters) and Stimulus.
Frequently asked questions about Crud Bundle
- What is symkit/crud-bundle used for?
- It is a Symfony bundle for adding consistent create, read, update, and delete workflows to applications with minimal boilerplate. It provides reusable CRUD controllers, configurable forms, and listing features such as pagination, search, and sorting. It is intended for admin-style resources and data-management screens where conventions reduce repetitive code.
- How do I install symkit/crud-bundle with Composer?
- Install it with Composer using the package name symkit/crud-bundle, then register the bundle in your Symfony application as described in the README. After registration, configure your resources and ensure routing and services are loaded. Always check the package composer.json for the required PHP and Symfony versions before installing.
- Does symkit/crud-bundle work with Laravel?
- No. symkit/crud-bundle is a Symfony bundle built around Symfony routing, services, controllers, and templates, so it is not a Laravel package. Laravel developers should look for a Laravel-specific CRUD or admin generator instead.
- Which Symfony and PHP versions are supported by symkit/crud-bundle?
- The supported Symfony and PHP versions are defined by the package composer.json constraints and release notes. Check those constraints before installing, because a bundle release may target a specific Symfony major version. If you are upgrading Symfony, verify compatibility in the repository first.
- How do I generate CRUD endpoints from a resource configuration?
- You define a resource configuration and the bundle uses reusable CRUD controllers plus Symfony-native routing and services to expose create, read, update, and delete endpoints. The exact configuration keys and route options should be taken from the package README. This keeps resource setup declarative while leaving custom behaviour in your application code.
- Can I customize forms, validation, and entity mappings?
- Yes. The bundle provides configurable forms, validation, and entity mappings so CRUD screens can match your domain model. For workflows beyond the defaults, you can extend actions and templates rather than fighting generated code. Keep application-specific logic in your own code and use the bundle conventions for the standard CRUD parts.
- Does the bundle include pagination, search, and sorting for listings?
- Yes. Built-in listing support covers pagination, search, and sorting, which is useful for admin panels and data-management screens. These behaviours are part of the bundle resource configuration and conventions. Check the README for the available options and how to customise the listing query.
- How do I override templates or extend CRUD actions?
- The bundle is designed to be extensible through actions and templates, so you can adjust the standard create, read, update, and delete workflows. In Symfony, template overrides and service or controller customisation follow the bundle documented conventions. Start with the README examples and keep overrides in your application rather than editing vendor code.
- How should I test CRUD routes and forms in a Symfony app?
- Use Symfony functional testing tools to request the generated routes, submit forms, and assert validation and redirect behaviour. Cover listing pagination, search, and sorting as well as create, update, and delete flows. Because the bundle integrates with Symfony routing and services, standard kernel or browser tests should fit the generated endpoints.
- Is symkit/crud-bundle production-ready and actively maintained?
- For production use, check the repository recent commits, releases, and open issues, and confirm the Symfony and PHP version constraints match your stack. The bundle is aimed at admin-style CRUD screens with reusable controllers, forms, listing features, and extensible templates. Compare it with other Symfony CRUD or admin generators based on maintenance activity, customisation needs, and long-term support.
Weaver
How can I help you explore Laravel packages today?