Skip to content
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] Avoid forcing to define the choices_as_values option when using choice_loader #22230

Merged
merged 1 commit into from Mar 31, 2017

Conversation

stof
Copy link
Member

@stof stof commented Mar 31, 2017

Q A
Branch? 2.8
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets n/a
License MIT
Doc PR n/a

When using the choice loader, choices are ignored entirely. Forcing the dev to add the choices_as_values just to avoid the deprecation warning (and then to remove the option again at some point in 3.x due to deprecation) is a bad developer experience.

…e_loader

When using the choice loader, choices are ignored entirely. Forcing the dev
to add the choices_as_values just to avoid the deprecation warning (and then
to remove the option again at some point in 3.x due to deprecation) is a bad
developer experience.
@stof stof changed the title Avoid forcing to define the choices_as_values option when using choice_loader [Form] Avoid forcing to define the choices_as_values option when using choice_loader Mar 31, 2017
@stof stof added this to the 2.8 milestone Mar 31, 2017
@stof stof added the Form label Mar 31, 2017
xabbuh
xabbuh previously approved these changes Mar 31, 2017
@xabbuh xabbuh dismissed their stale review March 31, 2017 12:07

looks like some tests need to be fixed

Copy link
Member

@xabbuh xabbuh left a comment

Choose a reason for hiding this comment

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

👍 (tests will fail without these changes too)

@stof
Copy link
Member Author

stof commented Mar 31, 2017

The failure is not related to my PR. It also fails in the 2.7 and 2.8 branches. See #22235 for the fix.

@fabpot
Copy link
Member

fabpot commented Mar 31, 2017

Thank you @stof.

@fabpot fabpot merged commit fb4d8de into symfony:2.8 Mar 31, 2017
fabpot added a commit that referenced this pull request Mar 31, 2017
…ion when using choice_loader (stof)

This PR was merged into the 2.8 branch.

Discussion
----------

[Form] Avoid forcing to define the choices_as_values option when using choice_loader

| Q             | A
| ------------- | ---
| Branch?       |2.8
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | n/a
| License       | MIT
| Doc PR        | n/a

When using the choice loader, choices are ignored entirely. Forcing the dev to add the choices_as_values just to avoid the deprecation warning (and then to remove the option again at some point in 3.x due to deprecation) is a bad developer experience.

Commits
-------

fb4d8de Avoid forcing to define the choices_as_values option when using choice_loader
@stof stof deleted the skip_useless_deprecation branch April 3, 2017 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants