-
Notifications
You must be signed in to change notification settings - Fork 245
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
util: add DestinationChip and DestinationInputChip components #3586
Conversation
Could you pls add to the description screenshots with the intended UX and the info for setup (experimental flag, mutation to have Dest types added, etc)? |
I updated the description to include screenshots and added additional context. This won't need any experiment flags to run. |
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 👍
a0e8f3d
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!
make check
to catch common errors. Fixed any that came up.Description:
This pull request introduces the DestinationChip and DestinationInputChip components, an addition that is essential for facilitating the development of generic destinations with pluggable providers. These components play a role in processing props such as icons, text, and cancel functions, and rendering them on the screen.
Which issue(s) this PR fixes:
Part of #2639
Screenshots:
Icon Variations:
Additional Info:
Run
make storybook
to interact with new components.These components will be unused in main application functions, until we have wired them in with future component updates, e.g. PolicyStepDialog components.