-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Form] Deprecate the "choices_as_values" option of ChoiceType #16994
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
[Form] Deprecate the "choices_as_values" option of ChoiceType #16994
Conversation
nicolas-grekas
commented
Dec 13, 2015
Q | A |
---|---|
Bug fix? | no |
New feature? | no |
BC breaks? | no |
Deprecations? | yes |
Tests pass? | yes |
Fixed tickets | - |
License | MIT |
Doc PR | - |
👍 |
Is there any way to "feature detect" whether or not this option needs to be set (to |
@craue |
@stof, thanks. I wonder why |
@craue because the changelog files are incomplete, as reported already. Latest removals have been forgotten |
…iceType (nicolas-grekas) This PR was merged into the 3.1-dev branch. Discussion ---------- [Form] Deprecate the "choices_as_values" option of ChoiceType | Q | A | ------------- | --- | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | yes | Tests pass? | yes | Fixed tickets | - | License | MIT | Doc PR | - Commits ------- 9aa5507 [Form] Deprecate the "choices_as_values" option of ChoiceType
I am using Symfony 3.1.2 and I receive the message: The "choices_as_values" option is deprecated since version 3.1 and will be removed in 4.0. You should not use it anymore. but I DON'T use "choices_as_values". I just use "choices" as shown below. Do I miss something ?
Stack trace in case it helps
|