Closed mustanggb closed 1 month ago
Thanks for the patch @mustanggb !
Did you also test this using Doctrine ORM and that still works?
I'd hold off on this for now, I've not had a chance to look into the failures etc.
If anyone else wants to investigate please do.
@mustanggb I see the tests about MongoDB also fails in master, as this contribution came from you could you have a look at this?
@johanwilfer Looks like it's a bug introduced by mongodb-odm 2.8.0 (https://github.com/doctrine/mongodb-odm/pull/2630), I believe it should be fixed in https://github.com/doctrine/mongodb-odm/pull/2671.
Do you want to wait for the fix, or we can temporarily workaround by requiring <2.8
(or similar).
I think the temp workaround sounds good, that way we get tests in master to not fail again.
If you want/can do it in this branch it should stop to fail and then we can merge this if that sounds good?
Done, unless you want them squashing into one commit.
I know GitLab supports that on merge/pull, not sure if GitHub does.
Alternatively keeping them separate would also for easy revert when the workaround is no longer needed, I'll leave it up to you.
Looks great!
And yeah, Github supports squashing of merged branches into one commit (this is how it is setup in the repro currently):
On a personal note I perfer individual commits in the feature branch to follow the process, and to squash on merge (to follow the PR).
When using pair history ORM is now optional not required.
Removing this should allow MongoDB users to use pair history without having the ORM package installed.