-
Notifications
You must be signed in to change notification settings - Fork 842
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
Beta XYChart Component #309
Conversation
Jenkins test this |
Nice work on this @chandlerprall and @mattapperson ! I've been busy with APM stuff this week - will try to make time next week to take a stab at this. |
@mattapperson I think we need to rewrite the From a DataViz perspective there is a difference between bar charts and histograms:
I'm looking through the Kibana issues but seems that no one noticed that creating a bar histogram like the following shows misunderstanding ticks in the x-axis (seems that the ranges are -500 bytes to 500 bytes, 500b to 1500b and so on, when the correct values are 0 - 1000, 1000 - 2000) (@timroes @ppisljar)
I think we can extend them having 4 EUIBars components or find a way for one configurable component. What do you think? |
@markov00 it seems to me it’s not about splitting the bar series, but simply adding 3 more? |
@mattapperson yes 3 more component and renaming the current one respecting its "vertical nature". So something like |
@markov00 Then yes, I fully support this |
Ok I will create a PR with these 4 components. I think we can also take this circumstance to fix exports and components naming (currently they are named |
@markov00 That would be great! it was on my todo list for tomorrow :) |
@chandlerprall @mattapperson I've updated my PR here. I think it's in a good shape and it's time to review it a bit before merging. |
package.json
Outdated
@@ -47,6 +47,8 @@ | |||
"react-datepicker": "v1.4.1", | |||
"react-input-autosize": "^2.2.1", | |||
"react-virtualized": "^9.18.5", | |||
"react-vis": "^1.9.3", |
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.
1.10.1 was released yesterday. Should we upgrade?
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.
Yes, strange that the package.json is not updated. I've upgraded react-vis and it's reflected into the yarn.lock.
@mattapperson could you please check and upgrade correctly?
I pulled Marko's latest updates and it LGTM |
We'll do a separate design PR. @chandlerprall Can you take a quick review of this? |
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.
Needs an entry to CHANGELOG.md , otherwise code and docs LGTM
Add a more generic BarSeries and HistogramSeries, controlled by XYChart orientation prop. Fixed Examples to use this convention instead of single Vertical/Horizontal components. Add the default margin to XYChart.
@chandlerprall I've updated the CHANGELOG. After the CI pass I will merge this ok? |
stroke-opacity: 0.3; | ||
// support a clean mouse over when grids is above elements | ||
pointer-events: none; | ||
} |
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.
@mattapperson @markov00 This rule caused some (minor) issues for the APM graphs so @formgeist overwrote this in:
elastic/kibana#21723
Not sure if the css is scoped by plugin or will affect all of kibana. Anyway, it seems suboptimal to overwrite styles like this. Any ideas for a better solution?
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.
Yeah, these kinds of styles should be scoped with some .eui---
classname. We haven't yet done a design audit of the new chart component. Sorry for the override, we'll make sure not to have generic library selectors after the audit.
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.
No worries. Just an fyi.
And sounds good with no generic library selectors.
Resolves #536
Items out of scope of current PR
Docs:
Nice to haves
Overall todo
General series todo
Chart component todo list