- Can I use alterphp/easyadmin-extension-bundle directly in a native Laravel project without Symfony?
- No, this bundle is designed for Symfony and requires Symfony’s DependencyInjection, EventDispatcher, and Doctrine ORM. For Laravel, you’d need to integrate Symfony components (e.g., `symfony/dependency-injection`) or use a hybrid approach like Lumen. Eloquent and Blade would also require custom adapters for Twig templates and Doctrine.
- What Laravel alternatives provide similar features (list filters, embedded lists, role-based access) with lower integration risk?
- Consider Laravel Nova, FilamentPHP, or Backpack for Laravel Admin Panel. These packages are natively built for Laravel’s Eloquent and Blade, offering comparable features like CRUD filters, nested resources, and permission systems without requiring Symfony dependencies. They’re also more actively maintained for modern Laravel versions.
- How do I install this bundle in a Laravel project using Symfony components?
- First, install required Symfony components via Composer: `symfony/dependency-injection`, `symfony/http-kernel`, and `doctrine/orm` (or `doctrine/dbal`). Then, create a Laravel Service Provider to bootstrap the bundle’s services. You’ll also need to adapt Twig templates to Blade or use a Twig bridge like `twig/twig`. Documentation for Symfony integration is limited, so expect trial-and-error.
- Does this bundle support Laravel’s Eloquent ORM, or is Doctrine required?
- This bundle relies on Doctrine ORM, which isn’t natively compatible with Eloquent. To use it with Laravel, you’d need to either: 1) Use Doctrine as a secondary ORM, 2) Create a data mapper layer to translate between Eloquent and Doctrine entities, or 3) Stick to Doctrine models only. Performance and query differences may arise between the two ORMs.
- What Laravel versions are officially supported by this bundle?
- This bundle doesn’t officially support Laravel—it’s for Symfony (4.2+/5.x). However, you *could* use it in Laravel 8+ by integrating Symfony’s Kernel and DI container, but this requires manual setup. For Laravel 9/10, compatibility isn’t guaranteed due to Symfony’s evolving dependencies. Test thoroughly in a staging environment.
- How do I handle Twig templates in Laravel if this bundle uses Twig?
- You’ll need to bridge Twig and Blade. Options include: 1) Install `twig/twig` and create a custom Blade-Twig adapter, 2) Use a package like `spatie/laravel-twig-view`, or 3) Rewrite Twig templates manually in Blade. Alternatively, extract the bundle’s logic (e.g., list filters) into standalone PHP classes and render views with Blade directly.
- Are there any breaking changes or deprecated features I should know about?
- Yes. The `3.x` branch introduces a BC break: list filters now use `ext_filters` instead of `filters` to avoid conflicts with EasyAdmin’s native dynamic filters. If upgrading from `2.x`, ensure your codebase reflects this change. Also, `2.x` doesn’t support EasyAdmin `2.2.0+`, so check your EasyAdmin version compatibility carefully.
- How can I test this bundle in a Laravel environment before full integration?
- Start with a Proof of Concept: 1) Isolate one feature (e.g., list filters) and test it in a Laravel + Symfony micro-service (e.g., Lumen). 2) Use Symfony’s `DependencyInjection` to load the bundle’s services in Laravel’s container. 3) Mock the EventDispatcher with Laravel’s Events system. 4) Test performance and edge cases (e.g., nested lists) in a staging environment before committing to full integration.
- What’s the maintenance status of this bundle, and should I rely on it long-term?
- The last release was in July 2022, with no recent updates or activity. The bundle isn’t actively maintained for modern Symfony or Laravel versions. If you proceed, monitor for upstream changes in EasyAdmin and be prepared to fork or adapt the code. Consider Laravel-native alternatives like FilamentPHP for long-term viability.
- Can I use this bundle’s features (e.g., list filters) without full Symfony integration?
- Yes, but it requires effort. Extract the bundle’s logic (e.g., filter classes) into standalone PHP classes and integrate them as Laravel services. For example, port the list filter logic to Eloquent query scopes or custom Blade components. This avoids Symfony dependencies but may not cover all features (e.g., embedded lists) without additional work.