Weave Code
Html Action Bundle Laravel Package
elao/html-action-bundle
Symfony bundle adding HTML CRUD and list actions for ElaoAdminBundle. Configure html_list/create/read/update/delete to generate admin routes and forms with optional security rules, providing ready-to-use backend pages for your entities.
Classic HTML actions for ElaoAdminBundle
Frequently asked questions about Html Action Bundle
- Can I use elao/html-action-bundle directly in a Laravel project without Symfony?
- No, this bundle is designed for Symfony and requires Symfony’s DependencyInjection, Twig templating, and Bundle architecture. Laravel’s native systems (Blade, service container) are incompatible without significant abstraction layers or a Symfony bridge, which isn’t officially supported.
- What Laravel alternatives provide similar HTML action functionality for admin panels?
- For Laravel, consider FilamentPHP, Nova, or custom Blade components with Laravel’s Form Requests and middleware. Packages like spatie/laravel-permission integrate with these tools for role-based actions. These avoid Symfony dependencies entirely and align with Laravel’s ecosystem.
- How do I install elao/html-action-bundle in a Laravel project?
- You cannot install it directly via Composer without Symfony. First, add Symfony’s DependencyInjection (`symfony/dependency-injection`) and Twig (`twig/twig`) as standalone packages, then manually configure a Symfony container alongside Laravel’s. This is complex and not recommended for new projects.
- Does this bundle support Laravel’s Eloquent ORM, or is it limited to Doctrine?
- The bundle assumes Doctrine ORM due to its Symfony roots. For Eloquent compatibility, you’d need to rewrite or abstract the data-layer logic, such as mapping Doctrine entities to Eloquent models. This adds significant maintenance overhead.
- Is elao/html-action-bundle compatible with Laravel 10+ and Symfony 6+?
- No, the last release was in 2017 and lacks updates for modern Symfony/Laravel versions. Symfony 6+ introduced breaking changes, and Laravel 10’s architecture diverges further. Using it risks dependency conflicts and security vulnerabilities.
- Can I replace Twig templates with Laravel Blade in this bundle?
- Not natively, but you could create a custom Twig-to-Blade compiler or rewrite the templates manually. The bundle’s `{{ action('...') }}` syntax would need Blade equivalents, and Symfony’s templating helpers (e.g., `{% form %}`) wouldn’t translate directly.
- What’s the performance impact of adding Symfony dependencies to Laravel?
- Adding Symfony’s DependencyInjection or Console components introduces overhead, including event dispatchers, service container lookups, and potential memory usage. For admin actions, this is often unnecessary—Laravel’s middleware and service container are lighter alternatives.
- Are there any tests or documentation for integrating this bundle with Laravel?
- The bundle lacks Laravel-specific tests or documentation. You’d need to reverse-engineer its usage via the elao/admin-bundle or fork the repository to adapt it. Expect undocumented edge cases, especially around Symfony-Laravel integration points.
- How can I migrate from elao/html-action-bundle to a Laravel-native solution?
- Start by auditing the bundle’s actions (e.g., bulk edits, quick links) and map them to Laravel equivalents: use Form Requests for validation, middleware for authorization, and Blade/Inertia.js for UI. Tools like FilamentPHP or Livewire can replicate admin panel functionality without Symfony.
- What’s the maintenance risk of using this bundle in production?
- High. The bundle is abandoned, with no updates for 6+ years. Symfony and Laravel evolve rapidly, so dependency conflicts or security patches are unlikely. Custom fixes for Laravel compatibility will require ongoing effort, making it less viable than native alternatives.
Weaver
How can I help you explore Laravel packages today?