Skip to content

Added explanation how non-scalar or non-unique choice values are handled #10507

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 1 commit into from
Oct 26, 2018
Merged

Added explanation how non-scalar or non-unique choice values are handled #10507

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 5 additions & 0 deletions reference/forms/types/choice.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,6 +188,11 @@ is the item's label and the array value is the item's value::
'choices_as_values' => true,
));

If there are choice values that are not scalar or the stringified
representation is not unique Symfony will use incrementing integers
as values. When the form gets submitted the correct values with the
correct types will be assigned to the model.

.. include:: /reference/forms/types/options/choice_attr.rst.inc

.. _reference-form-choice-label:
Expand Down