-
Notifications
You must be signed in to change notification settings - Fork 915
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
Split icon button toggling into its own component #370
Conversation
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.
Nice! Seeing all this code and imports disappear for the non-toggle version seems like a +1 for this refactoring, since I imagine a lot of users won't be using the toggle feature, and now they'll get a lighter build.
- This makes the non-togging case more lightweight - `<mwc-icon-button>` for non-toggling use cases remains the same - For toggling, use `<mwc-icon-button-toggle>` - `icon` is now `onIcon` Related to #348
4d8c9e9
to
c580ebe
Compare
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.
I'd be interested in creation benchmarks of boring icon button vs this button and toggle vs the old one with toggle on and both vs the old one as boring and as toggle on
Sounds good! I'll pull that into a new issue. |
Created #372 for benchmarking |
<mwc-icon-button>
for non-toggling use cases remains the same<mwc-icon-button-toggle>
icon
is nowonIcon
Fixes #369
Related to #348