Skip to content
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

Menu / Split button #1800

Draft
wants to merge 12 commits into
base: develop
Choose a base branch
from
Draft

Menu / Split button #1800

wants to merge 12 commits into from

Conversation

cnrudd
Copy link
Member

@cnrudd cnrudd commented Mar 27, 2020

Hoist P/R Checklist

Please view this branch with this corresponding toolbox branch:
https://github.com/xh/toolbox/tree/splitButton (toolbox PR )
Test page is at http://localhost:3000/admin/tests/button in toolbox
Demo page is http://localhost:3000/app/forms/toolbarForm in toolbox, to which I've added 3 split buttons.

Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

  • Caught up with develop branch as of last change.
  • Added CHANGELOG entry, or determined not required.
  • Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
  • Updated doc comments / prop-types, or determined not required.
  • Reviewed and tested on Mobile, or determined not required.
  • Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

+ Tweak prop names - for discussion
+ Install custom className on top-level buttonGroup / menu elements only
+ Be explicit about which subset of props we pass to the trigger button
+ Tighten up trigger sizing
@amcclain
Copy link
Member

Hi @cnrudd - thanks for opening this up.

I took a look and made some updates to discuss. More than anything, this made me realize that we don't have a basic (non-split) menu button in Hoist. I would like to review potential props with @lbwexler this coming week and then get in both the split and non-split buttons to show menus with a common approach.

We should also look at the mobile menu components, which have a model involved and see what we might want to reconcile so we have as common and consistent approach as possible for such a core component. Getting menus into the mainline is long overdue - this is a great prompt to get a first iteration done on that this week. Thanks!

@cnrudd
Copy link
Member Author

cnrudd commented Mar 30, 2020

Ok, reviewed and ran the changes. All good. Let me know if there's something else you'd like me to do with regard to this.

@amcclain
Copy link
Member

Great - thanks for looking. We can touch base with Lee when the three of us have a few moments.

I'd like to review the props as they are for this component, and then decide on a (hopefully) consistent approach that could also add in a menuButton component (exact name TBD). I think that latter component would be more commonly used, although I still want/love splitButton.

@amcclain amcclain marked this pull request as draft August 4, 2021 17:48
@amcclain amcclain changed the title Split button Menu / Split button Aug 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants