Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Dropping Icon component in favor of Material Design Icons for React
See original GitHub issueHello,
I would like to know if we could drop the actual implementation of Icon component to instead use Material Design Icons for React.
It has ALL of the original Material icons made by Google (which you can find here) plus some (a lot, actually) of community made one.
I’m asking this because I recently worked on a project which uses react-materialize and a lot of icons.
At first everything was fine, but soon I’ve realized I was in need of more icons than the one provided by Google (and consequently react-materialize implementation of Icon).
Then I discovered this library and it plays very well with react-materialize I can say.
But It’s strange to have two Icons component from two different packages which fulfill the same exact task.
What do you think?
This might be a really good enhancement for react-materialize!
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ok, going to have a look 😃
Hey, @alextrastero, I think we can make any
iconpropanodeand not usingIconcomponent ourselves in other components ofreact-materialize. If the user wants, he can use the component shipped withreact-materialize, otherwise he is able to use anythings he wants, likeMaterial Design Icons for React.This is the same approach used in #793 .
Let me know if this is ok for you, I’d like to open a P.R for this, if you agree. 😄