-
Notifications
You must be signed in to change notification settings - Fork 6
Create Select & Tooltip Components #85
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
Conversation
|
Deploy preview for helix-react ready! Built with commit fd7b466 |
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.
Thanks! A couple nits and questions...Storybook in Dark mode looks nice.
src/Select/stories.js
Outdated
| <Demo required /> | ||
| ); | ||
| }) | ||
| .add('Optional', () => { |
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.
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.
my "required, disabled" example might not have been the best demonstration of the point I was trying to make. But the knobs do offer a consistent approach to manipulating the components and can be themed.
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.
At the heart of this comment is just a desire to have an approach that's consistent for changing component state across the project. If we use use knobs, great! if we controls inside the canvas like the tool tip story, I can get behind that too. Just looking for a consistent approach, we can apply so all stories work in a similar way. What are your thoughts? If there are no strong opinions yet, we can deal with it latter when there is more of a knowing about which approaches seem to work better, might just mean a little more rework if we wait too long.
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.
@HelixDesignSystem/helix-react-core, I agree it's better to go with @nicko-winner's recommendation to have a consistent approach:
At the heart of this comment is just a desire to have an approach that's consistent for changing component state across the project. If we use use knobs, great! if we controls inside the canvas like the tool tip story, I can get behind that too. Just looking for a consistent approach, we can apply so all stories work in a similar way. What are your thoughts? If there are no strong opinions yet, we can deal with it latter when there is more of a knowing about which approaches seem to work better, might just mean a little more rework if we wait too long.
I defer to you all for the LOE between using knobs vs another approach, though it does seem like knobs provide (implementation) consistency and flexibility.
100stacks
left a comment
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.
@HelixDesignSystem/helix-react-core great work and discussions guys...we're making progress! 💯
src/Select/stories.js
Outdated
| <Demo required /> | ||
| ); | ||
| }) | ||
| .add('Optional', () => { |
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.
@HelixDesignSystem/helix-react-core, I agree it's better to go with @nicko-winner's recommendation to have a consistent approach:
At the heart of this comment is just a desire to have an approach that's consistent for changing component state across the project. If we use use knobs, great! if we controls inside the canvas like the tool tip story, I can get behind that too. Just looking for a consistent approach, we can apply so all stories work in a similar way. What are your thoughts? If there are no strong opinions yet, we can deal with it latter when there is more of a knowing about which approaches seem to work better, might just mean a little more rework if we wait too long.
I defer to you all for the LOE between using knobs vs another approach, though it does seem like knobs provide (implementation) consistency and flexibility.
PrettierI created a When you run Every time you do Our teams moves this into the webpack bundle pipeline so it becomes automatic but I'm deferring that here. If you add a prettier plugin to your code editor, that will also format against our prettier settings. I'm open to suggestions! |
|
@nicko-winner @100stacks this is ready for re-review |
nicko-winner
left a comment
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, but just noticed tooltip is missing some of the attributes / events. Can handle in a followup PR or address now.
|
|
||
| const Tooltip = ({ children, id, position }) => { | ||
| return ( | ||
| <hx-tooltip for={id} position={position}> |
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.
Can we add the events and attributes listed on this page: https://helixdesignsystem.github.io/helix-ui/elements/hx-tooltip/ ?
100stacks
left a comment
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.
Dev LGTM


Tooltip
Select
✅ Required and Optional variants