- Does incompass/soft-deletable-bundle work with Laravel?
- It is a Symfony bundle built for Doctrine ORM entities, not a Laravel/Eloquent package. Laravel ships with the native Illuminate\Database\Eloquent\SoftDeletes trait, so a standard Laravel app has no capability gap for this package to fill. Composer may install it, but Laravel will not auto-discover Symfony bundle wiring.
- How do I install incompass/soft-deletable-bundle?
- You can install it with composer require incompass/soft-deletable-bundle, but that only places the code in vendor. In Symfony you would enable the bundle and configure its Doctrine event subscriber and query filter. In Laravel, the symfony-bundle type is not auto-discovered, so installation alone does nothing.
- Is this package compatible with Laravel 10 or Laravel 11?
- There is no Laravel-specific integration or compatibility claim for Laravel 10 or 11 in the provided context. It targets Doctrine entities in Symfony, while Laravel 10 and 11 expect Eloquent for native soft deletes. If your app uses laravel-doctrine/orm, you would need to verify and manually wire compatibility yourself.
- Can I use it with laravel-doctrine/orm?
- Only with manual adapter work: register the package's Doctrine event subscriber and SQL filter inside a Laravel service provider. That bypasses the Symfony dependency-injection wiring the author actually tested. For Doctrine in Laravel, the maintained path is Gedmo SoftDeleteable configured through stof/doctrine-extensions-bundle, not this package.
- What happens if the Doctrine event subscriber is not registered correctly?
- Soft delete depends on intercepting EntityManager::remove() through an event subscriber. If the subscriber is misregistered, remove() degrades to a hard delete. Tests can still pass unless you explicitly assert that the row remains in the database after deletion, making this a silent data-loss risk.
- How does it compare to Gedmo SoftDeleteable?
- Gedmo SoftDeleteable uses the same Doctrine event model but is actively maintained, documented, and widely installed. It is commonly configured via stof/doctrine-extensions-bundle and has production validation this package does not show. For Doctrine-backed projects, Gedmo is the lower-risk choice.
- Does it support restore, withTrashed, onlyTrashed, or forceDelete?
- Those names are part of Laravel's Eloquent SoftDeletes API, not this Doctrine bundle. This package provides soft-delete and restore behavior at the Doctrine layer, not Eloquent query scopes or Laravel helper methods. If you need withTrashed(), onlyTrashed(), and forceDelete(), use Laravel's native trait.
- What PHP and Doctrine versions are supported?
- The provided repository context does not establish declared PHP or Doctrine version constraints. You should inspect the package composer.json and any CI configuration before assuming current compatibility. Evidence of ongoing compatibility testing was not found in the assessment.
- Is incompass/soft-deletable-bundle maintained and safe for production?
- Adoption signals are effectively zero: 0 stars, 0 dependents, no visible issue history, unknown release cadence, and an unconfirmed license. The dominant failure mode is quiet: deletes may hard-delete or reads may return deleted rows if wiring or filter configuration is wrong. Do not greenlight it without a named owner, a fork plan, and explicit post-delete row assertions.
- What should Laravel developers use for soft deletes instead?
- Use Laravel's native Illuminate\Database\Eloquent\SoftDeletes trait: add a nullable deleted_at column via migration and call delete(), restore(), withTrashed(), onlyTrashed(), or forceDelete() as needed. That requires zero third-party dependencies and no adapter work. If you are on Doctrine in Laravel, use Gedmo SoftDeleteable with the Doctrine filter configuration instead.