-
Notifications
You must be signed in to change notification settings - Fork 4
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
[Component] Integrate DS Select + Multiselect #206
Conversation
✅ Deploy Preview for cfpb-design-system-react ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
8d216cd
to
a3c16c8
Compare
a3c16c8
to
759a799
Compare
In talking with @natalia-fitzgerald I've learned there are other teams experimenting with the DSR so we'd like to merge the current progress we've made on integrating the DS Select/Multiselect into DSR with the understanding that we will pick up work on the pending issues once our proposed changed to the DS Multiselect are merged and released. Moving this PR into |
First errorFound this error when selecting items in the EDIT: I see you are aware of it here. Second errorComments@meissadia Nice work so far! I have a couple of questions/suggestions:
|
Good catch, this actually is a blocker to this component being useable, so we'll have to wait on merging these changes. This requires our DS PR to be merged, then for an update to the DS npm package to be released. That said, this PR should still be approved if things look good to avoid delays once the other dependencies are ready, we will simply wait to merge.
I've added the export of SelectSingle and SelectMulti so folks have the ability to directly import/use either one. I'm still a fan of having a consolidated Select for ease of use, with devs able to switch between functionalities with a single flag.
We've been working toward unifying the implementation of
👍🏾
There is nothing stopping implementors from passing a For SelectMulti, since we're leveraging the DS Multiselect which has it's own highly customized DOM element generation and event processing, we simply don't have the ability to control it. |
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.
Already noted the pending issues, however approving since this PR is just a phase 1.
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.
Upon review, the second error that I found in my comment is breaking the components' implementation and should be addressed before approval.
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.
Approving as requested.
Waiting on this PR to be merged and a new DS NPM version to be released with said PR changes. |
90f7fb4
@natalia-fitzgerald Updated. Would this be ready for "Verified" state? SidebarOverviewSingleMultiple |
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.
@meissadia
This is looking good. Just a couple of changes.
Instead of "Default" for the label text in the examples can we uss "Label"? Or do you think it would be more parallel with Text inputs to remove the label entirely?
In the DS we start with Option 1. What is Option 0?
- Update label from "Default" to "Label" - Update option names from 0 indexed to 1 indexed - Split options between Multi/Single
@natalia-fitzgerald I think we should keep the Label so end-users see that it's configurable.
|
|
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.
@meissadia The documentation and content look great!
I noticed that the DSR tag is slightly taller than the DS tag. I spoke to @meissadia about this. I am not sure how we want to proceed - whether we want to push live (draft state) and then troubleshoot this (and fix in a later PR) OR wait until this is fixed. We can discuss.
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.
Tested functionally and reviewed code. It is working great!
One minor story change.
…sier interaction with the menu
@natalia-fitzgerald Since this issue is likely to be affecting other components that involve Icon + Text, I propose we move forward with merging the changes implemented in this PR and then addressing the icon alignment in a follow-up ticket. I've opened #303 to track that investigation. |
Opened a follow-up ticket to investigate the issue: #303
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.
Looks great @meissadia!
Phase 1 for #197
Changes
How to test this PR
yarn vitest Select
Screenshots
Sidebar
Custom Overview
Single select Overview
Multiselect Overview