Weave Code
Data Grid Bundle Laravel Package
kitpages/data-grid-bundle
Kitpages DataGridBundle is a Symfony bundle for building configurable data grids with pagination, sorting, filtering, and customizable columns. It helps turn Doctrine queries or arrays into reusable, template-friendly grid views for admin and listing pages.
Symfony DataGridBundle
Frequently asked questions about Data Grid Bundle
- Is kitpages/data-grid-bundle compatible with Laravel?
- No, not out of the box. It is a Symfony bundle built around Bundle registration, a DependencyInjection extension loading services.yml, Twig rendering, and Doctrine query builders, none of which exist natively in a Laravel app. You could technically pull the code in via Composer, but every integration point would be hand-written glue. Treat it as a reference design to port, not a dependency to install.
- Can I install Kitpages DataGridBundle with Composer in a Laravel project?
- Composer may resolve it, but expect conflicts because its constraints target PHP 7.x-era and Symfony 3/4 components. On PHP 8.1+ or Symfony 6+ you should anticipate dependency resolution failures or runtime deprecations. Even if installation succeeds, there is no service provider or auto-discovery, so nothing is wired up for you.
- Does Kitpages DataGridBundle support Laravel 10, Laravel 11, or PHP 8.2?
- There is no evidence of support for any Laravel version, since the package was never a Laravel package. The last tagged release was 2019-03-27, which predates Laravel 10, Laravel 11, and modern PHP 8 runtimes. Six years of PHP and Symfony backward-compatibility breaks mean you should assume it does not run cleanly on current stacks without a fork.
- What is the portable part of Kitpages DataGridBundle worth reusing in Laravel?
- The genuinely reusable idea is the separation between a DataSourceInterface that yields paginated rows and a Grid and Column configuration object that controls labels and cell rendering. That core is framework-agnostic in principle and roughly 300 to 500 lines. The Doctrine ORMQueryBuilder source, Twig templates, and DI extension are Symfony-specific and would be discarded in a port.
- How do I build an Eloquent data source to replace the Doctrine one?
- Implement the same data-source contract with an EloquentDataSource and a QueryBuilderDataSource that return rows plus a total count. Delegate paging to Illuminate\Pagination\LengthAwarePaginator so page-size and page-number semantics match the rest of your app. The key detail is making the count query separate from the row query so pagination totals stay correct after filters are applied.
- What Laravel alternatives should I evaluate before porting a Symfony datagrid bundle?
- For server-rendered admin tables, look at Filament tables, Orchid, Backpack, or Livewire components before considering a port. For lighter product surfaces, plain Blade plus Laravel's query builder paginator and a small column-definition class is often enough. Evaluating these first tells you whether you need a grid abstraction at all or just a table.
- How do pagination, sorting, and filtering work in Kitpages DataGridBundle?
- The bundle reads sort and filter state from the Symfony request and applies it to a Doctrine query builder through the configured data source. Column definitions control which fields are sortable and filterable, and the grid renders the current page with paging controls. In a Laravel port you would rebuild that state handling on Illuminate\Http\Request and keep the same column configuration shape.
- Is Kitpages DataGridBundle safe to use in production?
- It is risky. The package is effectively unmaintained, with no releases since March 2019, no security patching, and zero dependents on Packagist validating it in production. Datagrids concentrate risk in dynamic column, sort, and filter handling, where SQL injection through user-supplied sort keys and filter operators is a classic failure mode. Unaudited 2019 code will not have hardened against modern expectations.
- Can I use the bundle's Twig grid templates with Laravel Blade?
- Not directly. The rendering layer is Twig templates shipped inside the bundle's Resources directory and resolved through Symfony's templating service. In Laravel you would rewrite the table, header, and pager markup as Blade views or components. Only the column metadata and row data contract carries over, not the template files themselves.
- How much effort is it to port Kitpages DataGridBundle's grid abstraction to Laravel?
- Plan for a fork-and-extract rather than an install. You would vendor or reimplement the grid definition object, the column definition, the paginator and state object, and the data-source contract, then write Eloquent and query-builder sources behind it. Because there is no Bundle class, service provider, or bundle registration in Laravel, all of the wiring is manual, so the effort estimate is an order of magnitude higher than adding a dependency.
Weaver
How can I help you explore Laravel packages today?