Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

[Form] Fix FormEvents::* constant and value matching #24631

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Oct 19, 2017
Merged

[Form] Fix FormEvents::* constant and value matching #24631

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0fc2282
fix the constant value to be consistent with the name
yceruto Oct 19, 2017
0ee856a
Update UPGRADE-4.0.md
yceruto Oct 19, 2017
944931a
Minor reword
javiereguiluz Oct 19, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Minor reword
  • Loading branch information
@javiereguiluz
javiereguiluz authored Oct 19, 2017
commit 944931af633ba6fe0d5a27763a563a0d798f0252
5 changes: 3 additions & 2 deletions 5 UPGRADE-4.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,8 +226,9 @@ Finder
Form
----

* The constant values of `FormEvents::*` have been renamed to match with its name.
May break rare cases where the event name is used rather than the constant.
* The values of the `FormEvents::*` constants have been updated to match the
constant names. You should only update your application if you relied on the
constant values instead of their names.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will cause UPGRADE-4.0 in master and 3.4 going out of sync no? Which btw is already happening (https://www.diffchecker.com/5W6GeCnZ).. again :-)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the upgrade entry should be updated in 3.4 too?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it should be synchronized

* The `choices_as_values` option of the `ChoiceType` has been removed.

Expand Down
Morty Proxy This is a proxified and sanitized view of the page, visit original site.