-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[RFC] Tests around reported cases over DDC-2524 #1570
Conversation
Hello, thank you for creating this pull request. I have automatically opened an issue http://www.doctrine-project.org/jira/browse/DDC-4018 We use Jira to track the state of pull requests and the versions they got |
@mnapoli so far I fixed the |
b1d540f
to
4d337f1
Compare
4d337f1
to
8ea62b9
Compare
[RFC] Tests around reported cases over DDC-2524
*/ | ||
public function addClass($class) |
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.
removing public properties is a BC break, which must not be done in minor releases. You broke doctrine/data-fixtures. Please add the methods back
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.
Agree here - the merge has to be reverted and delayed to 3.x :-(
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.
This class was never meant to be used by anyone else, not even other Doctrine projects.
data-fixtures
should copy the new class and use on its own
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.
Here is a more detailed reason why I think this should not be reverted and why data-fixtures
usage of the old class here is broken: doctrine/data-fixtures#212 (comment)
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.
A solution as been decided for this BC break ? We temporarily fix the Doctrine ORM version to 2.5.2 on our project.
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.
@fsevestre yes, we'll not revert this commit. Explanation is available at data-fixtures comment I left in previous message.
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.
@guilhermeblanco Does that mean this fix will land in the next 2.5.x release?
I've got a different issue with commit ordering that this PR solves, so I really need it soon.
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.
Upon further review, it looks like my issue is likely related to cyclic dependencies, which explains why this fix would solve my issue.
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.
It'll only land in 2.6, as this introduces a BC break for data-fixtures project.
Fixes #707