Weave Code
Crudit Bundle Laravel Package
2lenet/crudit-bundle
Symfony bundle to rapidly build configurable CRUD back offices with SB Admin layout. Provides list views with pagination, sorting, actions, exports and batch ops, plus datasources, filters, menus, workflows, maps, markdown and Twig helpers.
Crudit is a symfony complete crud system
Frequently asked questions about Crudit Bundle
- Can I use CruditBundle in Laravel even though it’s a Symfony package?
- Yes, but with adaptations. The bundle’s modular architecture (controllers, configs, datasources) aligns with Laravel’s MVC. You’ll need to replace Symfony’s Doctrine with Eloquent, Twig with Blade (via middleware or spatie/laravel-twig), and abstract Symfony’s DI system using Laravel service providers. Start with a single CRUD to validate the approach.
- How do I install CruditBundle in Laravel?
- Run `composer require 2lenet/crudit-bundle`, then install dependencies like Bootstrap 5 and Webpack Encore via npm. Configure Laravel’s asset pipeline (Mix/Vite) to replace Symfony’s Encore, and ensure your base template extends Crudit’s SB Admin layout. Note: Twig templates require translation to Blade or a Twig integration layer.
- What Laravel versions does CruditBundle support?
- The bundle itself targets Symfony, but Laravel 9+ can adapt it. Test compatibility with your Laravel version by checking if the bundle’s core classes (e.g., controllers, datasources) can be bound to Laravel’s service container. Eloquent integration may require custom datasource implementations for Doctrine-specific logic.
- How do I create a CRUD in Laravel using CruditBundle?
- Follow the Symfony docs for `make:crudit`, but replace Doctrine entities with Eloquent models. Define a config class for your CRUD, bind it to Laravel’s service container, and adapt the controller to use Laravel’s route model binding. Use Blade directives or middleware to render Twig templates if needed.
- Does CruditBundle work with Laravel’s Eloquent ORM?
- Not out-of-the-box, but it’s feasible. The bundle’s datasources assume Doctrine, so you’ll need to create custom adapters to bridge Eloquent’s query builder or repositories. Start by replacing Doctrine’s QueryBuilder with Eloquent’s `where()`, `orderBy()`, etc., and adapt the FilterSet class to use Laravel’s query scopes.
- How do I handle Twig templates in Laravel?
- Use a package like `spatie/laravel-twig` to integrate Twig with Blade, or convert Crudit’s Twig templates to Blade manually. Focus on isolating Twig usage to minimal components (e.g., modals) and replace dynamic blocks (e.g., `{% block stylesheets %}`) with Blade equivalents or JavaScript DOM injection.
- Can I customize the SB Admin layout for Laravel?
- Yes, but you’ll need to adapt the Twig templates to Blade. The layout’s CSS/JS (Bootstrap 5, Webpack Encore) can be integrated via Laravel Mix or Vite. Replace Symfony’s asset pipeline configurations with Laravel-compatible ones, and ensure SCSS imports align with your project’s structure.
- What are the performance implications of using CruditBundle in Laravel?
- Performance depends on your adaptations. Symfony’s DI and event system may introduce overhead if not abstracted properly. Optimize by lazy-loading CRUD configs, caching datasource queries, and using Laravel’s query builder efficiently. Test batch operations and exports under load, as these rely on heavy data processing.
- Are there alternatives to CruditBundle for Laravel CRUDs?
- Yes, consider Laravel-native packages like `spatie/laravel-permission` (for role-based CRUDs), `backpack/crud`, or `orchid/software`. For Symfony-like features, `filp/whoops` (error pages) or `laravel-excel` (exports) can complement custom CRUDs. CruditBundle’s strength lies in its advanced UI components (batch actions, maps, markdown), which may not be fully replicated elsewhere.
- How do I test CruditBundle in a Laravel project?
- Test feature parity by creating a minimal CRUD and validating core functions (pagination, sorting, exports). Use Laravel’s testing tools (e.g., `Http::actingAs()`) to simulate user flows. Mock Symfony-specific dependencies (e.g., EventDispatcher) with Laravel’s service container. Focus on critical paths like data persistence and UI rendering.
Weaver
How can I help you explore Laravel packages today?