[5.1] Tag Cloud should deal with empty responses correctly#9367
Closed
elastic-jasper wants to merge 1 commit into5.1from
Closed
[5.1] Tag Cloud should deal with empty responses correctly#9367elastic-jasper wants to merge 1 commit into5.1from
elastic-jasper wants to merge 1 commit into5.1from
Conversation
Backports PR #9354 **Commit 1:** Tag Cloud should deal with empty responses correctly tag cloud did not work with empty responses correctly. One of the side-effects is that the back button did not work properly. For example, pressing the back button would not empty out the screen and show stale clouds. This also caused a type-error. Empty configurations meant that we could not access any aggregation-configs to produce a label. * Original sha: 9b52ba4 * Authored by Thomas Neirynck <thomas@elastic.co> on 2016-12-02T22:58:54Z
Contributor
|
closing, needs #9372. This is going to require manual backport. |
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.
Tag Cloud should deal with empty responses correctly
Backports PR #9354
Commit 1:
Tag Cloud should deal with empty responses correctly
tag cloud did not work with empty responses correctly. One of the side-effects is that the back button did not work properly. For example, pressing the back button would not empty out the screen and show stale clouds.
This also caused a type-error. Empty configurations meant that we could not access any aggregation-configs to produce a label.