-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any plans to release a new version compatible with doctrine 3.x? #2808
Comments
It's a work in progress, see #2708 |
This would really be great to work with Doctrine 3, there's other packages that are now dependent on it (like the latest version of https://github.com/stof/StofDoctrineExtensionsBundle). The version of the bundle that works with this library (1.10) has a __call() method that no longer matches the signature here, so I'm uncertain how to update. @stof ? |
That code doesn't exist in the bundle, it's in this library. And if you're referring to the repository class I think you are, then #2758 already fixed it. There are plenty of pull requests opened by me dealing with an overwhelming majority of the compatibility issues, and anything not covered yet by a PR will be once the current queue is cleared and I can re-sync with my working branch with all the changes needed without any B/C layer. I don't have merge rights on this repo, and as I've said repeatedly, I do not work on open-source contributions with any form of sponsored time (be it through GitHub sponsorships or corporate backing), so I'm doing what I can when I can. I'm sorry that's not enough for everyone. |
Thanks, @mbabker, for your PRs and work on this. Indeed, I see that #2758 has been merged, but I can't figure out how to get it working in my Symfony 7.1 project. If you a fork or branch that might work, I'd be happy to use/test it. I am confused about stof's bundle v. this library, to the point of trying to switch to Knp's Doctrine Behaviors, but it, too, doesn't work in 7.1 except via a fork. |
This library provides the Doctrine extension behaviors and is framework agnostic. https://github.com/stof/StofDoctrineExtensionsBundle adds the glue code to get it running in the context of a Symfony application. It's not much different than the relationship between There aren't any issues with this library or |
Thanks. I guess I have a dependency somewhere on orm 3 or dbal 4. Something changed between .10 and .11, gut feeling is that is has to do with annotations, but I'm stabbing a bit here. stof/StofDoctrineExtensionsBundle@v1.10.1...v1.11.0 I'll see what happens when I force my app to be the version of orm and dbal that match this library. Thanks again. |
The |
For those who are interested to test it, you can update your "doctrine/orm": "^3.0",
"gedmo/doctrine-extensions": "dev-main", And then, run |
@Seb33300 |
@andreybolonin you can use it without bundle https://github.com/doctrine-extensions/DoctrineExtensions/blob/main/doc/symfony.md |
@andreybolonin the actual issue is that the development version is |
And another issue is that the branch alias for |
There has been a new release: https://github.com/doctrine-extensions/DoctrineExtensions/releases/tag/v3.16.0 |
Feature Request
The current version is not compatible with doctrine 3.x, mainly due to the use of annotations and other small things.
Even though doctrine 3 was released only last February, I think it's worth it to release a compatible version early for those like me who like to use the newest version when starting a new project.
The work to be done is not really huge, and I am volunteering to be part of it.
The text was updated successfully, but these errors were encountered: