-
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
show drop partial buckets option #25520
Conversation
Pinging @elastic/kibana-app |
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. Tested locally on chrome/OSX.
Can you add a simple functional test for this option?
|
||
const expectedChartValues = [37, 202, 740, 1437, 1371, 751, 188, 31, 42, 202, 683, | ||
1361, 1415, 707, 177, 27, 32, 175, 707, 1408, 1355, 726, 201, 29 | ||
]; |
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 think it's better to change this test as the following:
- create a bar chart with a different timestamp than the standard one (one that contains partial buckets)
- test the expected values before applying the
drop partial bucket
option - apply the
drop partial bucket
option - test and expect a smaller amount of values as expected data.
So we can test either the partial bucket option checkbox and the functionality
💔 Build Failed |
b9c6c1e
to
0e0d39f
Compare
💔 Build Failed |
retest |
💔 Build Failed |
seems a legit fail:
|
0e0d39f
to
3df64bd
Compare
💚 Build Succeeded |
Summary
Check for showing 'show partial buckets' option was broken, this fixes it.
resolves #25521
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.[ ] This was checked for cross-browser compatibility, including a check against IE11[ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support[ ] Documentation was added for features that require explanation or tutorials[ ] This was checked for keyboard-only and screenreader accessibilityFor maintainers
[ ] This was checked for breaking API changes and was labeled appropriately[ ] This includes a feature addition or change that requires a release note and was labeled appropriately