Skip to content

Conversation

@acasar
Copy link
Contributor

@acasar acasar commented Mar 3, 2016

Following #12572 I think it's best to do it in 5.3 then.

@taylorotwell @vlakoff

@vlakoff
Copy link
Contributor

vlakoff commented Mar 3, 2016

The feature doesn't work so I think it's not a problem to remove it in 5.2.

And if someone was extending performUpdate or performInsert protected methods, as the parameter was optional this shouldn't be breaking under normal circumstances.

@GrahamCampbell
Copy link
Collaborator

5.3 is fine imo.

@acasar
Copy link
Contributor Author

acasar commented Mar 3, 2016

@vlakoff We can still remove the feature from 5.1 and 5.2 without modifying method parameters, but I'm not sure if it's worth it.

@acasar
Copy link
Contributor Author

acasar commented Mar 3, 2016

No idea why tests are failing :/ But it seems unrelated to this PR.

@GrahamCampbell
Copy link
Collaborator

Try rebasing your fork.

@mark86092
Copy link
Contributor

The build fail due to the change of symfony class, I send a PR #12623.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants