- Does rafwell/laravel-simplegrid support Laravel 10 and PHP 8.2?
- The available package overview does not publish a clear Laravel and PHP version matrix, so verify compatibility yourself before adopting it. Create a scratch Laravel app on your target versions and run composer require rafwell/laravel-simplegrid to inspect the illuminate/* and PHP constraints. If the package lags your Laravel version, decide up front whether to fork it under MIT or choose another grid solution.
- How do I install rafwell/laravel-simplegrid in a Laravel application?
- Install it with Composer and rely on Laravel package discovery, then publish the package config, Blade views, and public assets. Define your grid classes, mount them on admin routes, and render them from controllers that return Blade views. A one-day spike is realistic for getting a single screen working end to end.
- Does laravel-simplegrid require jQuery or DataTables, and does it work with Vite?
- The overview describes a Blade rendering layer with client-side enhancement, but it does not confirm whether jQuery or DataTables is required. Review the published public assets and JavaScript before committing, and test them against your Vite or Mix pipeline. Treat any older asset assumptions as an integration risk that needs a quick compatibility spike.
- How do search, sorting, and pagination work in laravel-simplegrid?
- The package turns an Eloquent query into a declarative grid definition with columns, filters, and actions, then handles pagination, sorting, and search for the rendered table. Confirm whether those operations run server-side and inspect the generated SQL for each interaction. Also check how relationship columns are eager-loaded so you do not hide N+1 queries behind the grid.
- How do I enforce per-grid and per-row authorization with laravel-simplegrid?
- Authorization is almost certainly the host application's responsibility rather than something the package enforces. Protect grid routes with your existing middleware and policies, and apply per-row visibility rules in the underlying query or grid definition. Wrapping each grid behind an internal base class makes it easier to centralize those checks consistently.
- Can laravel-simplegrid handle Eloquent relationships, global scopes, and multi-tenant queries?
- The package is built around Eloquent queries, but the overview does not guarantee support for every query feature you use. Test relationship columns, global scopes, subqueries, and tenancy constraints against a real screen before rollout. If the declarative abstraction restricts complex queries, keep that logic in your own query builder and pass a constrained query into the grid.
- Is rafwell/laravel-simplegrid safe from SQL injection in search and filter handling?
- Any package that builds column and filter handling from request strings warrants an explicit SQL-injection review. Check how search terms, sort columns, and filters are validated, and prefer allowlists for sortable columns. Do not assume safety; inspect the query layer and add tests for malicious input before using it in production.
- Can I use laravel-simplegrid in an API-only, Inertia, or SPA application?
- No, it is a presentation-layer package designed for Blade-rendered admin screens on a Laravel monolith. It has low value in headless APIs or front ends owned by a JavaScript framework such as Vue, React, or Inertia. Use it where the controller returns a view and the grid owns pagination, sorting, and search.
- What are good alternatives to rafwell/laravel-simplegrid for Laravel admin tables?
- Consider actively maintained options such as Livewire table packages, server-side DataTables integrations, or Filament for strategic admin surfaces. For a handful of CRUD listings, this lightweight package can be cheap and sufficient. For a long-lived admin area, compare maintenance, testing, and upgrade overhead before standardizing on it.
- Is rafwell/laravel-simplegrid actively maintained and production ready?
- The project has a small footprint and a single maintainer, with an unclear release and CI cadence, so maturity is the main risk rather than complexity. Published views and assets mean upgrades are manual merges instead of a clean composer update. If you adopt it, wrap it behind an internal base class or trait and confirm the MIT license lets you fork if maintenance stops.