This repository was archived by the owner on Apr 12, 2024. It is now read-only.
fix(select): assign result of track exp to element value#9718
Closed
jeffbcross wants to merge 1 commit into
Closed
fix(select): assign result of track exp to element value#9718jeffbcross wants to merge 1 commit into
jeffbcross wants to merge 1 commit into
Conversation
Fixes a regression where the option/select values would always be set to the key or index of a value within the corresponding collection. Prior to some 1.3.0 refactoring, the result of the track expression would be bound to the value, but this behavior was not documented or explicitly tested. This commit adds one explicit test for this behavior, and changes several other trackBy tests to reflect the desired behavior as well. Fixes angular#9592
Contributor
Author
|
@tbosch FYI |
Contributor
|
LGTM |
jeffbcross
pushed a commit
to jeffbcross/angular.js
that referenced
this pull request
Oct 29, 2014
Fixes a regression where the option/select values would always be set to the key or index of a value within the corresponding collection. Prior to some 1.3.0 refactoring, the result of the track expression would be bound to the value, but this behavior was not documented or explicitly tested. A cache was added in order to improve performance getting the associated value for a given track expression. This commit adds one explicit test for this behavior, and changes several other trackBy tests to reflect the desired behavior as well. Closes angular#9718 Fixes angular#9592
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Fixes a regression where the option/select values would always be set to
the key or index of a value within the corresponding collection. Prior to
some 1.3.0 refactoring, the result of the track expression would be bound
to the value, but this behavior was not documented or explicitly tested.
This commit adds one explicit test for this behavior, and changes
several other trackBy tests to reflect the desired behavior as well.
Fixes #9592