-
Notifications
You must be signed in to change notification settings - Fork 355
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
Fix for support on different Doctrine ORM versions #414
Conversation
This is a BC which we do not allow for v1. Can we ensure that both are supported here? |
@pimjansen I can try and do the same doctrine did and add a |
Correct. For v2 we will remove it from core and can be a community driven extension instead. |
Apparently, psalm is failing in CI but not on my machine using the same PHP version.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 1 week if no further activity occurs. Thank you for your contributions. |
Hope it will be fixed soon, thanks :) |
@icanhazstring the pipeline is failing, can you review this? |
@pimjansen see this comment. |
No idea but ci is leading so needs to be green |
@icanhazstring Running psalm locally is red for me too, works with this psalm.baseline.xml: https://gist.github.com/krsriq/cc1c3ceea2886aa4b93a2b1825a32e7f |
@krsriq then there is something weird with the local setup 🤷♂️ Guess I'll just add your baseline then. |
Add doctrine/orm as dev dependency to avoid baseline entries.
After all these years. |
@icanhazstring is this ready now? |
@bram-pkg checked it again against my problem. Fixed for me 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, also test on 1.3 and 2.x went fine
This PR caused an issue on projects that don't utilize
It seems that FakerPHP expect |
It was added to But the other case you are correct. Will create a quick fix for that. |
@crynobone fix has been applied in main |
Add conflict to doctrine/persistence below 1.4 and use correct persistence classes
What is the reason for this PR?
Fix an issue with
doctrine/persistnce
Author's checklist
Summary of changes
Add a conflict intocomposer.json
fordoctrine/persistence
below version 1.4composer.json
fordoctrine/orm
Adddoctrine/orm
as dev requirement to avoid static analysis baseline entriesUse new classes ofdoctrine/orm
anddoctrine/persistence
forFaker\ORM\Doctrine
namespaceclass_alias
forClassMetadata
andObjectManager
Review checklist