-
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
EuiDualRange component #1485
EuiDualRange component #1485
Conversation
@nreese @thomasneirynck Let me know your thoughts on the API, specifically the returned |
@thompsongl love it! Array with 2 numbers works for me. As for the input-element having the value, that's fine imho. That is also probably something we do not really have to worry about from a user perspective, correct? (ie. that the dual-range component is implemented using |
@thomasneirynck Great! |
@thompsongl Let me know when you've been able to
Then I can do a more thorough review. At first glance (not at the code) I just saw a couple of issues:
|
@cchaos will do.
|
|
@thompsongl Looks really nice. Need some error handling for when Since this PR refactors EuiRange so much. Should I just close #1461 and let you migrate those ideas in this PR? |
@nreese @chandlerprall @cchaos I've incorporated the concepts from #1461 and addressed all other feedback. Re: Validation:
|
The other thing that #1461 did was to allow the inputs to be completely empty. Right now when you delete the contents it always reverts to Your PR: His PR: I will make a note to myself that we need to flesh out the docs and break apart the examples for this component. But that can come later so that we can unblock the Kibana implementation. |
|
||
&__progress { | ||
height: 4px; | ||
border-radius: 4px; |
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.
Note to @snide : I'll do a follow-up PR to clean up PX values. Not sure when/why they were never variables to begin with.
@chandlerprall I've fixed the first 3 of your comments. Good catch on that front! I'm working through options for the last one. |
Updates for the last comment from @chandlerprall |
@snide @cchaos thoughts on the modified classes? e.g. https://github.com/elastic/eui/pull/1485/files#diff-7ff6102775c5757cab5eb3e9443c3bff |
Hmm, there are some class changes that look concerning especially in the jest files, though I thought they looked right when I reviewed (like compressed). I'll have to take another look. |
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.
Just a couple small things. Nice refactoring though!!
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; reviewed code changes and tested UX. Going to hold off on approval until @cchaos takes a second look at those classnames.
Re: class name changes: Could be that this isn't your concern, but more context for you all, nonetheless. |
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. Just had a couple questions about multiple components in one file.
Name change suggestion from @cchaos Co-Authored-By: thompsongl <[email protected]>
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.
Great, Thank you! Sorry it took so long. I know others will be excited for this one.
Summary
Resolves #496
EuiRange
into smaller, shareable components (no breaking changes unless you count class names)EuiDualRange
that usesEuiRange[X]
componentsChecklist
Incorporate changes from EuiRange - onValidatedChange props #1461
This was checked in mobile
This was checked in IE11
This was checked in dark mode
Any props added have proper autodocs
Documentation examples were added
A changelog entry exists and is marked appropriately
This was checked for breaking changes and labeled appropriately
Jest tests were updated or added to match the most common scenarios
This was checked against keyboard-only and screenreader scenarios
- [ ] This required updates to Framer X components