[Form] ArrayChoiceList can now deal with a null in choices #17511
+8
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
re-create for mistaken #17502
Documentation says, since 2.7, choice value is treated as corresponding item value (if
choices_as_values
option is true). Null as well.But actually null doesn't work as expected since
ArrayChoiceList::getChoicesForValues()
usesisset
to check whether given value exists in its choices.It should use
array_key_exists
instead to do so here.