-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugfix: Fix TS to avoid assigning filters to undefined #40249
Merged
lizozom
merged 2 commits into
elastic:master
from
lizozom:bug/filter-manager/assign-filters-to-undefined
Jul 3, 2019
Merged
Bugfix: Fix TS to avoid assigning filters to undefined #40249
lizozom
merged 2 commits into
elastic:master
from
lizozom:bug/filter-manager/assign-filters-to-undefined
Jul 3, 2019
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
lizozom
added
bug
Fixes for quality problems that affect the customer experience
v8.0.0
Team:AppArch
release_note:skip
Skip the PR/issue when compiling release notes
v7.3.0
labels
Jul 3, 2019
Pinging @elastic/kibana-app-arch |
💚 Build Succeeded |
ppisljar
approved these changes
Jul 3, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code LGTM
lizozom
force-pushed
the
bug/filter-manager/assign-filters-to-undefined
branch
from
July 3, 2019 15:32
eebd1a2
to
4afca7e
Compare
💔 Build Failed |
💚 Build Succeeded |
lizozom
pushed a commit
to lizozom/kibana
that referenced
this pull request
Jul 3, 2019
* Define getAppState TS correctly, to avoid filter assignment into an undefined state * Added tests for the case where appState is undefined
spalger
pushed a commit
that referenced
this pull request
Jul 4, 2019
spalger
pushed a commit
to spalger/kibana
that referenced
this pull request
Jul 12, 2019
* Define getAppState TS correctly, to avoid filter assignment into an undefined state * Added tests for the case where appState is undefined
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Fixes for quality problems that affect the customer experience
release_note:skip
Skip the PR/issue when compiling release notes
v7.3.0
v7.4.0
v8.0.0
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
Angular is responsible for initializing appState asynchronously.
This means that filter_state_manager might sometimes get a null \ undefined AppState.
The class's TypeScript didn't reflect this and had a place that assigned filters to AppState, without checking if it's defined.
Should resolve #40220
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.For maintainers