- Is siganushka/generic-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle built on Symfony 7.4 components, not a Laravel package. Its CRUD abstractions, Twig filters, KnpPaginator decoration, and kernel response listener assume Symfony's HttpKernel and Form contracts. Laravel teams should treat it as a conditional dependency and verify any portable subset before adoption.
- How do I install siganushka/generic-bundle?
- Install it with Composer using composer require siganushka/generic-bundle. In a Symfony app, register the bundle in config/bundles.php if it is not auto-registered. Laravel will not auto-discover it as a package, so there is no standard service provider registration path. Check the repository README for the exact bundle class and configuration files.
- Does siganushka/generic-bundle support Laravel 10 or Laravel 11?
- There is no native Laravel 10 or Laravel 11 support because this is a Symfony bundle. Laravel 11 aligns with the PHP 8.2 floor, but the Symfony 7.4 requirement can conflict with Laravel's pinned Symfony component ranges. A Laravel 10 service on PHP 8.1 is immediately out of scope.
- Can I use siganushka/generic-bundle CRUD controllers in a Laravel app?
- Probably not cleanly. The CRUD route-generation traits assume Symfony routing conventions, so they will not drop into Laravel's router without adaptation. Only framework-agnostic pieces such as date range value objects or test doubles are likely portable. Scope any Laravel usage to verified portable features and do not assume Twig, KnpPaginator, or normalizer coverage.
- What PHP and Symfony versions does siganushka/generic-bundle require?
- The package requires PHP 8.2 or newer and Symfony 7.4. The PHP floor fits Laravel 11+ but strands Laravel 9 and 10 services still on PHP 8.1. The Symfony 7.4 floor is the larger risk because Laravel pins its own Symfony component ranges, so run a Composer dry run against your lock file first.
- How do I configure a Doctrine entity for CRUD with siganushka/generic-bundle?
- You declare a Doctrine entity as a resource and provide resource metadata so the generic controller knows how to expose it. The bundle then generates predictable create, read, update, and delete routes and handles requests consistently. Exact configuration keys depend on the bundle's resource metadata classes, so verify them against the repository README and source.
- Does siganushka/generic-bundle include filtering, sorting, and pagination?
- Yes, the package advertises built-in filtering, sorting, and pagination support. Pagination is tied to KnpPaginator decoration in the Symfony release notes, so it is not a framework-agnostic feature. In a Laravel app, you would need to replace or bypass that layer rather than expect it to work as-is.
- How do I test CRUD endpoints built with siganushka/generic-bundle?
- For Symfony, test the generated CRUD routes through functional tests that exercise each action against a test database. The package includes MockAuthenticator test doubles that can help with authenticated request scenarios. For Laravel, you would need to verify which test utilities are decoupled from Symfony's security and HttpKernel contracts before relying on them.
- What breaking changes should I check before upgrading to siganushka/generic-bundle 1.2.0?
- Treat 1.2.0 as a breaking upgrade despite the minor version number. The renames knp_current_page_number to knp_current_page and currentPageNumber to currentPage break Twig templates and paginator call sites, and Nestable is now abstract. JsonResponseListener::onKernelResponseForNoContent() was removed, so audit any reliance on 204 handling before upgrading.
- Is siganushka/generic-bundle production-ready, and what are the alternatives for Laravel?
- For Symfony applications on PHP 8.2+ and Symfony 7.4, it can be production-ready after you handle the 1.2.0 breaking changes and test 204 response behavior. For Laravel, it is not a drop-in CRUD solution; consider Laravel-native packages or hand-written resource controllers instead. If you only need portable test doubles or value objects, evaluate whether that narrow subset justifies the dependency.