Weave Code
Symfony Entity Utils Bundle Laravel Package
halloverden/symfony-entity-utils-bundle
A Symfony bundle offering assorted helper utilities for Doctrine entities, including common traits and convenience methods that reduce boilerplate. Lightly adopted with limited documentation, so review the source and test coverage before relying on it in production.
At a glance
Frequently asked questions about Symfony Entity Utils Bundle
- Can I use halloverden/symfony-entity-utils-bundle in a Laravel application?
- No, not directly. It is a Symfony bundle built on Symfony's kernel and dependency-injection extension system, and Laravel has no equivalent construct, so composer require will not give you working behavior in a Laravel app. The only viable path is harvesting the PHP traits out of the bundle and discarding the Symfony configuration layer.
- How do I install halloverden/symfony-entity-utils-bundle with Composer?
- Run composer require halloverden/symfony-entity-utils-bundle and, in a Symfony app, register the bundle in config/bundles.php. There is no bundles.php step in Laravel because bundles do not exist there. Check the repository's composer.json for version constraints before you install.
- What traits and entity helpers does this bundle actually provide?
- The documentation is thin, so treat the source as the definitive list. The overview describes assorted helper utilities for Doctrine entities, typically traits and convenience methods for things like timestamps, UUID or ULID identifiers, blameable fields, soft deletes, slugs, and versioning. Confirm the actual trait set by reading the repository before you plan around it.
- Does this package work with Laravel Doctrine or Eloquent models?
- Eloquent is out of scope because these are Doctrine entity helpers, and there is no Laravel service provider. With laravel-doctrine you could theoretically reuse the traits if they are pure PHP, but the bundle plumbing is dead weight and the realistic integration path is a re-implementation, not an install.
- Which PHP, Symfony, and Doctrine versions does it support?
- The declared constraints live in the repository's composer.json, not in the marketing copy, so read them directly. The package is low-activity, so verify the constraints still resolve on your target PHP and Doctrine versions. Symfony bundle configuration APIs changed across major versions, so the Symfony constraint matters as much as PHP.
- Does it add Doctrine lifecycle callbacks, and can they conflict with my existing listeners?
- The bundle is entity utilities, so Doctrine lifecycle callbacks or event subscribers are plausible, but ordering relative to your existing listeners is undocumented. Callback order is order-sensitive, and getting it wrong can silently change persistence behavior. Audit the trait and subscriber code before enabling it alongside listeners you already rely on.
- Is halloverden/symfony-entity-utils-bundle safe for production?
- Treat it as unproven for production. It has one star, no dependents, a single maintainer, and limited documentation, which means no implicit compatibility testing against Symfony, Doctrine, or PHP upgrades. A two-hour source read and a local test run are the minimum before you rely on it.
- How does it compare to stof/doctrine-extensions-bundle or writing my own entity traits?
- stof/doctrine-extensions-bundle is the mature, widely adopted option for soft deletes, slugs, timestamps, and blameable behavior in Symfony. Writing your own traits in Laravel is often cheaper than forking this one, roughly one to two days for timestamp, UUID, and soft-delete traits with tests. Fork-and-strip is strictly more expensive than writing it yourself unless the trait list turns out to be larger than it appears.
- Is the package still maintained, and what is its license?
- The license is MIT, confirmed in the repository. Maintenance signals are weak: bus factor one, no visible governance, and no ecosystem dependents, so check whether issues and pull requests get answered. If the repo is dormant, plan to own and fork the code yourself.
- How should I audit or test the bundle before depending on it?
- Start by reading composer.json for constraints, then the trait source to see whether it references Symfony DI, EventDispatcher, or Config components, because that decides portability. Run the test suite locally and check CI coverage, and confirm whether the traits prescribe column types such as UUID as binary(16) or char(36). Also check trait headers for attribution and copied code before adopting anything.
Weaver
How can I help you explore Laravel packages today?