Fix EuiComboBox activeOptionIndex error#1695
Merged
Merged
Conversation
Contributor
|
jenkins test this (CI failure is a known somewhat flaky test) |
7 tasks
7 tasks
Shigawire
pushed a commit
to Shigawire/eui
that referenced
this pull request
May 10, 2019
* change activeOptionIndex pattern; guard against -1 * elastic#1695 changelog entry
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
Fixes #1693 (
activeOptionIndexerror with empty search results). See error reproduction steps in the issue.activeOptionIndexto always be a number (-1instead ofnullorundefined). This is just for logic simplification.activeOptionIndexof-1Checklist
- [ ] This was checked in mobile- [ ] This was checked in IE11- [ ] This was checked in dark mode- [ ] Any props added have proper autodocs- [ ] Documentation examples were added- [ ] This was checked for breaking changes and labeled appropriately- [ ] This was checked against keyboard-only and screenreader scenarios- [ ] This required updates to Framer X components