- What is dejwcake/admin-listing used for in Laravel?
- It is a lightweight Laravel package for building admin listing screens for Eloquent models. It provides configurable columns, filters, and row actions so you can add consistent, reusable data tables and management views to Laravel admin panels. It is most useful for database-backed admin listings, catalogs, and moderate-volume search screens.
- How do I install and configure dejwcake/admin-listing?
- Install it with Composer using composer require dejwcake/admin-listing, then follow the repository README for any configuration publishing or registration steps. Columns, filters, and row actions are defined through the package's listing configuration rather than hard-coded tables. Pin the version you validate and commit your lockfile.
- Which Laravel and PHP versions does dejwcake/admin-listing support?
- The provided materials do not publish an official Laravel or PHP support matrix, so confirm the exact constraints in the package composer.json and CI matrix. Release 2.1.0 adds test coverage and a CI matrix, which improves confidence but does not replace checking your application versions. The package is aimed at Laravel applications using Eloquent for admin listings.
- How does accent-insensitive search work in dejwcake/admin-listing?
- Release 2.1.0 augments ListingService with database-native accent-insensitive matching. On MySQL and MariaDB it relies on utf8mb4 with a suitable collation such as utf8mb4_unicode_ci, and on PostgreSQL it uses the unaccent extension when available. Without unaccent, PostgreSQL falls back to case-insensitive ILIKE, so behavior can vary by environment.
- How do I opt out of accent-insensitive search on MySQL/MariaDB or PostgreSQL?
- The provided materials do not document a MySQL/MariaDB opt-out comparable to dropping unaccent on PostgreSQL. Review the package source and configuration hooks for a way to limit accent-insensitive matching to selected columns or search paths. Until that is confirmed, test behavior in staging and consider restricting search at the application level.
- Will upgrading to 2.1.0 change my existing Laravel listing search results?
- Potentially yes, because accent-insensitive matching returns broader result sets for accented text. Existing tests, saved searches, and user expectations may need updating even though 2.1.0 is a minor-version release. Treat the upgrade as a behavior change and validate result sets for accented and non-accented queries.
- How should I test an upgrade to dejwcake/admin-listing 2.1.0?
- Pin the version, run your application test suite against MySQL/MariaDB and PostgreSQL, and add result-set tests for accented queries such as Uložiť and Ulozit. In staging, test PostgreSQL both with and without the unaccent extension to expose environment drift. Review generated SQL and EXPLAIN plans on representative data before production rollout.
- What are the performance risks of accent-insensitive search in Laravel admin listings?
- CONVERT, unaccent, and CAST expressions can make search predicates non-sargable and may bypass indexes on large tables. The evaluation specifically asks for query plans or benchmarks showing index usage after these changes. Test EXPLAIN plans on production-like data and consider applying accent-insensitive search only to selected text columns.
- What alternatives to dejwcake/admin-listing should I consider?
- Broader Laravel admin frameworks include Laravel Nova, Filament, and Backpack, while custom Blade tables remain an option for simple needs. If your product needs relevance ranking, faceting, or high-volume search, pair a database-backed listing with Elasticsearch, Meilisearch, or OpenSearch rather than replacing it. dejwcake/admin-listing is best treated as a lightweight listing layer, not a full search engine.
- How is dejwcake/admin-listing maintained and what should I know before upgrading?
- Release 2.1.0 is a minor-version change with low-to-moderate integration effort for existing 2.x consumers, and it adds test coverage plus a CI matrix. The CI MariaDB 12.2 image may be newer than production, so confirm supported database versions rather than assuming compatibility. Pin the package, review the changelog and source for query changes, and validate configuration and query semantics before upgrading.