siganushka/generic-bundle
siganushka/generic-bundle offers reusable generic components for Symfony/PHP projects, helping streamline Doctrine-backed resource setup with shared traits and CRUD helpers. It reduces repetitive boilerplate and keeps application structure consistent and easy to extend.
composer update, bin/console cache:clear.CRUD traits, SerializerDumpCommand, and the Twig/form/paginator integration points.SerializerDumpCommand to inspect the generated serialization config as YAML.knp_current_page / currentPage before deploying.CRUD traits to generate or standardize route/controller boilerplate. Keep project-specific authorization and validation in your controller rather than inside the trait.SerializerDumpCommand in local/dev or CI to dump serialization metadata to YAML. Commit or diff that file when serialization groups/configuration change.DecoratingKnpPaginator when you need custom page metadata, query params, or template variables without forking paginator logic.DateRange and DateRangeType for date-filter forms, reports, and admin list screens. Normalize the range into start/end boundaries before passing it to repositories.MockAuthenticatorFactory and MockAuthenticator to simulate authenticated users without building full security tokens manually.FormErrorNormalizer with the new form_error_with_errors context when API clients need nested field errors instead of a flat error list.highlight Twig filter for search-result snippets, but pass already-escaped content or explicitly control escaping based on your template policy.knp_current_page_number to knp_current_page, and PHP code from currentPageNumber() to currentPage().knp_current_page_number and currentPageNumber were renamed. Search templates and PHP for old names before upgrading.JsonResponseListener::onKernelResponseForNoContent() was removed. If you relied on automatic JSON handling for 204 No Content, return explicit responses or add your own listener.Nestable is now abstract. Extend it instead of instantiating it directly; check any custom subclasses or service definitions.CRUD traits are convenient but can create route/controller conflicts. Review generated routes and naming before enabling them across an existing app.SerializerDumpCommand output is best treated as a debugging/CI artifact. Avoid hand-editing generated YAML unless the package documents it as a source of truth.MockAuthenticator* should only be enabled in test/dev environments; ensure service registration does not leak into production.highlight Twig filter can introduce XSS risk if used with raw user input. Prefer escaped output and test with HTML-bearing search terms.How can I help you explore Laravel packages today?