Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Crudl Controller

Crudl Controller Laravel Package

softspring/crudl-controller

A Laravel package offering a reusable CRUDL controller base for create, read, update, delete, and list actions, helping developers scaffold admin resources faster and reduce repetitive controller boilerplate.

View on GitHub
Deep Wiki
Context7

A CRUD+list helper classes

Frequently asked questions about Crudl Controller
Does softspring/crudl-controller work with Laravel?
No. softspring/crudl-controller is a Symfony bundle, not a Laravel package. It has no service provider, facade, Eloquent adapter, or Blade view layer for Laravel. Using it in a Laravel application would require a custom adapter that you would own and maintain.
Is softspring/crudl-controller a Laravel package or a Symfony bundle?
It is a Symfony bundle. It depends on Symfony HttpKernel, Form, and Doctrine components and is registered through config/bundles.php. The common framing of it as a Laravel package is incorrect and should be corrected before evaluation.
How do I install softspring/crudl-controller?
In a Symfony application, install it with Composer, register the bundle, import its routes, and configure your CRUDL resources. You should confirm the package's PHP and symfony/* constraints against your runtime before assuming a drop-in install. There is no supported Laravel installation path.
Which Symfony and PHP versions does softspring/crudl-controller support?
Version 5.x historically tracks current Symfony majors and pins Symfony and PHP version ranges. You must check the package's composer.json constraints against your exact PHP runtime and Symfony minor version. Laravel version support does not apply because this is not a Laravel package.
Can I use softspring/crudl-controller with Eloquent models?
No. The package is built around Symfony and Doctrine conventions, and it does not provide an Eloquent adapter. Laravel's Eloquent ORM is not supported without a substantial custom bridge. For Laravel applications, a Laravel-native CRUD solution is the appropriate choice.
What changed between softspring/crudl-controller v5.5.10 and v5.6.0?
The published changelog body for v5.6.0 is only a compare link, with no commit list or migration notes. A minor bump should be additive under SemVer, but without human-readable notes you cannot distinguish new configuration from behavioral changes in routing or pagination. Pull the diff and classify each commit before upgrading.
Is softspring/crudl-controller safe for production Laravel applications?
It is not viable for Laravel production use without a bespoke adapter, and that adapter would be entirely your maintenance burden. For Symfony applications it has standard Composer exposure, but there is no indication of signed releases or provenance attestation. Evaluate bus factor, changelog opacity, and upgrade cost before adopting it.
How do I test controllers built with softspring/crudl-controller?
In Symfony, test through functional tests using the kernel browser or WebTestCase, plus unit tests around your configuration and hooks. Pay particular attention to pagination, filtering, form handling, and URL generation because CRUD abstraction regressions often appear as subtly wrong results rather than hard failures. Laravel has no supported test path for this package.
What are alternatives to softspring/crudl-controller for Laravel CRUD scaffolding?
Laravel developers should use Laravel-native options such as resource controllers, Filament, Laravel Nova, or Backpack. softspring/crudl-controller is Symfony-only and does not integrate with Laravel resource routes or Blade. Bridging it into Laravel is a separate adapter project with no upstream support.
Who maintains softspring/crudl-controller and what is its release cadence?
It is maintained by the small vendor Softspring with a narrow contributor base. The release process does not currently produce human-readable changelog notes, which raises the cost of future upgrades. Review the issue-response history and release cadence over the last 12 months before depending on it.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource