-
Notifications
You must be signed in to change notification settings - Fork 27
Add tag builder options #621
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
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "@puppet/react-components", | |||
"version": "5.33.9", | |||
"version": "5.34.9", |
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.
should this not go to 5.34.0 ??
Also make sure to add an entry into the change log to explain whats in this release.
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.
It should! Thanks, Luke.
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.
Pulled down and tested, all looks good and great to get in. Added a small comments but will approved as will still be okay
* Add tag filter * Add focus helpers * Cleanup & lint * Split popup menu into its own component * Add detail component * Update search menu to use Detail component * Add docs and fix issues * Add menu tests * lint * Add lodash to dependencies * Bump & lint * Update snapshot * Update changelog * Fix version
Description of proposed changes
No breaking changes. Just adding a few components.
Adding:
<Detail />
A menu dropdown component we used in Relay and have meant to add. Doing it now because some compliance mocks are using it for the new menus.<Menu />
A component for quickly building custom menus and managing menu-item focus. It's not meant to replace theButtonSelect
or theActionSelect
, but it allows us to build more complex & product-specific menus faster going forward.<Menu.Search />
Built using the previous two components, it displays and groups options in a searchable/filterable menu. I thought it might be useful outside of Tag-specific usage.<Tag.Search />
Built using the previous three components, it usesMenu.Search
, for searching tags and displaying the selected ones. The compliance mock can be found hereScreenshot of proposed changes
Detail
Menu
Menu.Search
Tag.Search