You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just realized that the options "type" and "options" in CollectionType are rather ambiguous. Maybe we can add the aliases "entry_type" and "entry_options" to make them more readable:
… (WouterJ)
This PR was merged into the 2.8 branch.
Discussion
----------
[2.8] [Form] Rename CollectionType options for entries
Description
---
Replaces #13820 for the 2.8 branch.
Original description:
> `type` and `options` are extremely generic. Prefixing them with `entry_` makes it clear what they are configuring.
> About the property deprecation it is the same story as #13717 and I don't know which direction you want me to go.
I've tried to apply the comments in the previous PR, but got a bit lost in the normalizers/default closure stuff. I hope I did everything correctly, but please review :)
PR Info Table
---
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | yes
| BC breaks? | no
| Deprecations? | yes
| Tests pass? | yes
| Fixed tickets | #7831
| License | MIT
| Doc PR | symfony/symfony-docs#5051
Commits
-------
942a237 Rename CollectionType options for entries
I just realized that the options "type" and "options" in CollectionType are rather ambiguous. Maybe we can add the aliases "entry_type" and "entry_options" to make them more readable:
Especially in big forms, it's hard to understand the exact form structure with the current naming.
The text was updated successfully, but these errors were encountered: