Expose icons as named exports for consumers of package #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…wn icon colors to template, and styles to template
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I quite like the Icons in this package. I wanted to create my own custom AlertTemplate, but still make use of the icons without doing a copy paste of code from this repository.
This pull request does a small refactor which bunches up all the icons as named exports from an index file in the 'src/icons' directory and moves the AlertTemplate to its own file. The 'src/index' file is then changed to be the entry point for the build, and is where AlertTemplate is exported as default, and the icons are exported as named exports.