- How do I install fsi/datagrid in a Laravel application?
- Run composer require fsi/datagrid. Because the package is not Laravel-native per the TPM assessment, you may need to register service providers or write adapters manually. Before installing, audit 2.1.0 Composer constraints for PHP 8 minor versions, Symfony 5.x components, doctrine/persistence >= 1.3, and PSR dependencies.
- Does fsi/datagrid support Laravel Eloquent models?
- The package overview advertises Eloquent-backed grid sources, but the technical assessment notes Laravel integration still requires adapters for Eloquent/query-builder data sources. Expect to map models or query builders into the package's data-source contract. Full collection hydration may be needed, so test performance with large datasets.
- Which Laravel versions are compatible with fsi/datagrid 2.1.0?
- The TPM assessment does not confirm specific Laravel versions; it warns that 2.1.0 is a Symfony-oriented compatibility release with partial Symfony 5.x support. You must validate Composer constraints against your Laravel version's Symfony and Doctrine dependencies. Projects pinned to older Laravel/Symfony/Doctrine transitive dependencies may not upgrade without broader platform changes.
- Is fsi/datagrid a Laravel-native package?
- No. Although the overview describes Laravel/Eloquent/Blade usage, the technical assessment states it remains Symfony-oriented rather than Laravel-first. Laravel integration requires adapters for the service container, data sources, Blade/API rendering, routing, authorization, filtering, sorting, and pagination. Consider Laravel-native alternatives like Filament tables, Livewire tables, or Laravel DataTables first.
- How do I define columns and filters in fsi/datagrid?
- You define columns, filters, and row actions in PHP classes, then render them in Blade with sensible defaults for sorting and pagination. The package provides configurable columns and custom cell rendering. However, the TPM assessment notes undocumented extension points, so expect to read source code or tests for advanced configuration.
- Can I use fsi/datagrid with Blade templates?
- The overview says it is Blade-friendly and renders tables with minimal code. But the TPM assessment says Laravel integration still requires adapters for Blade/API rendering, suggesting the Blade integration may not be seamless. Test rendering, authorization, and edge cases in a proof of concept.
- What are the production risks of using fsi/datagrid in Laravel?
- The technical assessment rates technical risk as high for strategic adoption, citing limited ecosystem validation, partial Symfony 5.x support, stale or conflicting transitive dependencies, and security exposure through old dependencies. It recommends wrapping the package behind an internal Grid interface and feature-flagging a pilot with rollback. Do not let package-specific column objects leak across your application.
- Does fsi/datagrid support server-side sorting, filtering, and pagination?
- The package overview advertises sortable, paginated results with search and filter support. The TPM assessment asks whether pagination, filtering, and sorting are server-side and whether it supports Eloquent/query-builder data sources without full collection hydration. Confirm these behaviors in a time-boxed proof of concept before relying on them for large datasets.
- Is fsi/datagrid actively maintained and tested?
- The TPM assessment notes limited ecosystem validation and calls 2.1.0 a narrow compatibility release rather than evidence of sustained feature investment. It asks whether tests and documentation are sufficient to fork safely and what the fallback is if upstream maintenance stalls. Treat adoption as an isolated adapter project and plan for a fork or replacement.
- What are Laravel-native alternatives to fsi/datagrid?
- The TPM assessment recommends Laravel-native options such as Filament tables, Livewire tables, Laravel DataTables, or custom Blade/API grid components. These align better with Eloquent, policies, validation, and frontend conventions. Consider fsi/datagrid only if its column abstraction materially reduces bespoke rendering work and its 2.1.0 dependency constraints cleanly resolve in your app.