- Is omasn/doctrine-fixes-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. It ships a Bundle class, a DependencyInjection extension, and service configuration meant to be registered in config/bundles.php. Laravel has no equivalent bundle concept, so this cannot be dropped into a standard Laravel app as a native package. The only route into Laravel is a project already running Doctrine plus a hand-rolled compatibility shim.
- Can I install omasn/doctrine-fixes-bundle in Laravel with Composer?
- You can run composer require, but installation is not integration. The package's service definitions rely on Symfony container features such as tagged services and compiler passes that Laravel's container cannot resolve. A stock Laravel app has no composer require path that results in working behavior. Treat it as a source-reading exercise rather than an install.
- Does omasn/doctrine-fixes-bundle work with laravel-doctrine/orm?
- Not out of the box. Even in a Laravel project already running Doctrine through laravel-doctrine/orm, the bundle expects the Symfony kernel to register it and merge its configuration. You would need a shim to emulate bundle loading, which is effectively a re-implementation. The event subscribers and DBAL type overrides inside it are the portable part; the Symfony wrapper is not.
- What fixes are included in the RUVENTS Doctrine Fixes Bundle?
- The package collects practical workarounds for common Doctrine ORM issues around entity mapping, schema handling, and database behavior. Typical contents for a fixes bundle are Doctrine event subscribers, DBAL type overrides, and hydrator patches. The README excerpt is empty here, so read the source to catalogue exactly which fixes ship in this fork. Do that before assuming any specific bug is covered.
- Which Doctrine ORM and Symfony versions does this bundle support?
- The last release was 2023-02-07, which predates Doctrine ORM 3.x and Symfony 7. It likely relies on 2.x-era ORM internals such as UnitOfWork and hydrator signatures that have changed since. There is no visible version matrix, CI, or compatibility statement in the repository. Assume ORM 2.x and confirm by reading composer.json and the source.
- Is omasn/doctrine-fixes-bundle safe to use in production?
- The adoption signal is effectively zero: about 2 stars, 0 dependents, and a package score near 0.01. It is a single-maintainer fork of a RUVENTS internal bundle with no visible CI, security policy, or release cadence. Fixes packages are especially risky because an upgrade can silently stop applying a patch instead of erroring. It would likely fail a standard OSS intake review before any code-level discussion.
- How do I register a Symfony bundle in Laravel?
- You cannot register a Symfony bundle in Laravel, because Laravel uses service providers rather than bundles. There is no config/bundles.php equivalent, and Laravel's container does not run Symfony compiler passes. The realistic approach is to re-implement the specific fix you need as a Laravel service provider plus a Doctrine event subscriber. That is usually 50 to 150 lines of code.
- What is the best alternative to omasn/doctrine-fixes-bundle for Laravel?
- Port the fix rather than the package. Read the bundle source, identify the specific listener, subscriber, or type override that solves your bug, and re-implement it in a Laravel service provider. Alternatively, vendor the MIT-licensed classes into your codebase with attribution and add your own tests. If you run a genuine Symfony application, the bundle shape is correct there and that is the one context where consuming it as-is makes sense.
- How do I write a failing test for a Doctrine bug before porting the fix?
- Reproduce the mapping, schema, or query behavior against your current Doctrine ORM version in a test that fails for the expected reason. Then port only the fix that makes that test pass, and keep the test in your own repo as a regression guard. This matters because a third-party fixes package can stop being applied after an upgrade without throwing an error. The test tells you the workaround is still needed and still working.
- Is omasn/doctrine-fixes-bundle still maintained?
- The last release is from February 2023 and there is no visible release cadence, CI, or security policy. It is published under a single maintainer handle as a fork of a RUVENTS internal bundle. Provenance and attribution questions for the forked MIT code are worth raising with the maintainer. For planning purposes, treat it as unmaintained.