[Dropdown] Preselected values are ignored when data has individual value-name #285
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…en setting initial selected elements.
lubber-de
added
lang/javascript
y0hami
removed
the
state/awaiting-reviews
This was referenced Dec 21, 2018
Merged
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Description
When a datastore has a different name for the
valuefield, all probably preselected values will not be assigned initially to the dropdown. That's because it was always expecting its name being calledvalueinstead of respecting a probably changed name insettings.field.value.Thanks @patilkiranm for the original PR
Testcase
Fixed Version
https://jsfiddle.net/pf2ae8cn/
Unfixed Version
https://jsfiddle.net/pf2ae8cn/1/
Closes
Semantic-Org/Semantic-UI#6682