-
Notifications
You must be signed in to change notification settings - Fork 712
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
Support icon as component instead of only image #895
Comments
Hi, is there any change to have this? thanks! |
Added to our board |
Hey @thebergamo and @dhcmega, |
I believe all components that have option to pass a image could benefit from being able to pass a component to it :) |
@lidord-wix hi! Out of the top of my head, I think I would use it as transparent back button for the header, regular buttons, lists and custom touchable buttons for the "home/desktop" of my app. Thanks! |
@lidord-wix @ethanshar I think I'm facing a similar issue - trying to pass an icon coming from |
Hey @richardrobberse, |
TabBar.Item is another candidate for this. I've even tried using the react-native-vector-icons getImageSource to pass the image directly to it
|
@thebergamo, @dhcmega, @richardrobberse, @mlabrum, |
Hi, can we get support for this for the Toast component "icon" prop? |
Hi @ConnorLanglois, |
Hello. Firstly, thanks for this library and the docs and examples. Really enjoying using it. I’m wondering if there is support or plans to add support for using icons from Or, if it is possible to load specific icons using Assets.loadAssetGroup that would allow them to be used in iconSource. Thanks |
Hello @MLaidlawScott, |
Hi,
First of all, after getting know this lib I fall in love, so cheers guys!
Would you be open to support passing icon in those components as component instead of supporting only images.
For example when we've the Chip component we would use it like this:
I believe it's quite standard using
react-native-vector-icons
, so we could have a more connected ecosystem.If you're open to have it as an option into those components, I would create a PR for it :)
The text was updated successfully, but these errors were encountered: