-
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
fixed editor state updates for parent pipeline aggs #22874
Conversation
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.
Pulled PR and tested locally. I can resolve the visualization configuration error now.
Two small comments on the added functional tests.
Approve after changes/comments and CI pass.
|
||
const error = await find.byCssSelector('.vis-editor-agg-error'); | ||
const errorMessage = await error.getProperty('innerText'); | ||
log.debug(errorMessage); |
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.
Could you add this in as a function in the visualize_page
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.
i am not a huge fan of putting functions that are never reused in there, but i can move it.
💚 Build Succeeded |
💔 Build Failed |
jenkins, test this |
💚 Build Succeeded |
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.
LGTM on IE and Firefox
3d18e83
to
fa6b6d9
Compare
💚 Build Succeeded |
resolves #22833
release notes: editor now correctly shows errors for parent pipeline aggregations
qa: create a vertical bar chart, choose derivative as a metric and add date histogram bucket agg.
after this add another bucket agg, select split rows, terms, any field ... before you wouldn't get an error, you could apply the change and get elasticsearch error. after this nothing worked.