Weave Code
Entity List Bundle Laravel Package
nfqde/entity-list-bundle
nfqde/entity-list-bundle is a Symfony bundle for building reusable entity lists with configurable data sources, filters, sorting, pagination, and rendering helpers, simplifying admin and backend list screens.
Doctrine entities listing, filtering and paging
Frequently asked questions about Entity List Bundle
- Can I install nfqde/entity-list-bundle in a Laravel application?
- No. It is a Symfony bundle that depends on bundle registration, Symfony's DI container and config-tree extensions, Symfony Request parsing, and Doctrine QueryBuilder assembly. A standard Laravel app has no bundle lifecycle and uses Eloquent by default, so there is no clean integration path. Even on a Laravel plus Doctrine hybrid, most of the installed code is Symfony wiring you would not use.
- How do I install and register nfqde/entity-list-bundle?
- You install it with Composer and register it as a bundle in config/bundles.php, or in AppKernel on older Symfony versions. You then define list configurations as services and render them through Twig helpers. This workflow is Symfony-specific and does not translate to Laravel service providers. Because the package is archived, verify composer.json constraints before attempting any install.
- Does nfqde/entity-list-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony and Doctrine ORM, not Laravel. There is no Laravel service provider, no Eloquent support, and no Laravel version constraint to satisfy. For Laravel 10 or 11, use a native approach such as spatie/laravel-query-builder with Laravel pagination instead.
- What does nfqde/entity-list-bundle do for pagination, sorting and filtering?
- It lets you declare entity list definitions with columns, filters, sortable fields, and page size, then compiles them into filtered, paginated Doctrine queries. Filter, sort, and paging values are read from the request query string, and results can be rendered as Twig tables. Treat the request-driven surface carefully: allowlist sort and filter columns and bound the page size.
- Is nfqde/entity-list-bundle safe for production?
- Treat it with caution. The repository is archived, so there are no security patches, compatibility updates, or advisory feed, and every transitive Doctrine CVE becomes your ticket. Request-driven filter keys, sort columns, and page sizes are a classic injection and denial-of-service vector unless validated and allowlisted. There is also no test-coverage signal to rely on.
- What are the best alternatives to nfqde/entity-list-bundle for Laravel admin lists?
- For Laravel, use spatie/laravel-query-builder for allowlisted filter, sort, and include parsing, combined with Laravel's built-in pagination and Blade or Inertia tables. If you need the abstraction, reimplement the declarative list-definition concept natively rather than porting this code. For Symfony projects, consider maintained admin tools such as EasyAdmin instead.
- Does nfqde/entity-list-bundle work with PHP 8.2 and modern Symfony?
- Compatibility is unproven. The Bundle naming and pre-Flex packaging strongly suggest Symfony 2 or 3-era code with PHP 5.6 or 7.x constraints. Because the package is archived, no PHP or Symfony compatibility updates have been made. Read composer.json and the last commit date before assuming it runs on PHP 8.2 or current Symfony.
- Do I need Doctrine ORM to use nfqde/entity-list-bundle?
- Yes. The bundle builds lists from Doctrine entities and assembles Doctrine QueryBuilder queries, so Doctrine ORM is a hard requirement. Laravel's Eloquent models are not supported. Even in a Laravel plus Doctrine hybrid, the Symfony bundle wiring layer would remain largely unused.
- Is nfqde/entity-list-bundle actively maintained and tested?
- No. It is archived, with zero stars and zero dependents, and there is no public test-coverage signal or issue history to learn from. There is no maintainer to escalate to and no upgrade path. The MIT license does allow forking, but you would own all maintenance from day one.
- Should I fork nfqde/entity-list-bundle or rebuild the entity list feature?
- For a Laravel application, rebuild it. The durable asset is the declarative list-definition contract, not the Symfony-specific implementation, and that contract is small and testable on your native stack. Forking carries Symfony and Doctrine-era constraints plus full maintenance ownership, even though the MIT license removes licensing concerns. Use the package as a design reference only.
Weaver
How can I help you explore Laravel packages today?