Skip to content
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

[7.x] [Resolver] Stale query string values are removed when resolver's component instance ID changes. (#74979) #75038

Merged
merged 1 commit into from
Aug 14, 2020

Conversation

oatkiller
Copy link
Contributor

Backports the following commits to 7.x:

…onent instance ID changes. (elastic#74979)

The app can show more than 1 Resolver at a time. Each instance has a unique ID called the `resolverComponentInstanceID`. 
When the user interacts with Resolver it will add values to the query string. The query string values will contain the `resolverComponentInstanceID`. This allows each Resolver to keep its state separate. When resolver unmounts it will remove any query string values related to it.

If Resolver's `resolverComponentInstanceID` changes it should remove query string values related to the old instance ID. It does not. This PR fixes that. 

Note: I don't know if it was possible for this bug to actually happen. I can't make it happen, but depending on how Resolver is mounted by its consumers it *could*
@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

@kbn/optimizer bundle module count

id value diff baseline
securitySolution 1909 -126 2035

async chunks size

id value diff baseline
securitySolution 7.2MB -143.4KB 7.3MB

page load bundle size

id value diff baseline
securitySolution 805.9KB -5.0B 805.9KB

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@oatkiller oatkiller merged commit e16d712 into elastic:7.x Aug 14, 2020
@oatkiller oatkiller deleted the backport/7.x/pr-74979 branch August 14, 2020 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants