Fixed bug when using queryForCurrentValue with multi-selects #502
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
|
👍 |
|
Changes Unknown when pulling c1d7ec2 on TheOtherDude:multi-select-queryForCurrentValue-fix into ** on ciena-frost:master**. |
|
👍 |
|
Changes Unknown when pulling 556bc29 on TheOtherDude:multi-select-queryForCurrentValue-fix into ** on ciena-frost:master**. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
This project uses semver, please check the scope of this pr:
This is a fix for the issue I referenced (and then mysteriously struck out) in this comment: #496 (comment)
I'm not sure why I thought the multi-select worked that way. It could have been related to a recently fixed select dropdown bug (or perhaps just temporary insanity).
CHANGELOG
ember-test-utilsNPM devDependency to^8.1.0package-lock.jsonuntil we officially support Node 8