[ML] Check for the sort field type in Anomalies table before updating the URL state.#98270
Merged
darnautov merged 2 commits intoelastic:masterfrom Apr 26, 2021
Merged
Conversation
Contributor
|
Pinging @elastic/ml-ui (:ml) |
15 tasks
Contributor
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @darnautov |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Apr 26, 2021
… the URL state. (elastic#98270) * [ML] check sort field type * [ML] functional tests for anomalies table pagination
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Apr 26, 2021
… the URL state. (elastic#98270) * [ML] check sort field type * [ML] functional tests for anomalies table pagination
Contributor
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
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 #98117
The regression has been introduced in #97350.
The column name is defined as a tooltip, which resulted in the

onChangecallback to receive it as afieldvalue instead of the string definition.I added a check for a string type, but I assume the actual issue is on the EUI side, as it should check for the
fieldproperty instead of thenamewhen fires theonChangecallback.Important observation: When I perform sorting by

severityby clicking on a column header, theonChangecallback receives a correct payload.Checklist