Ricky
You don’t really need it since you can create custom components and do whatever you want
1 1
Samuel
we had issues in the past where you can’t have a controlled input in a portalled component controlled from outside of the parent, because passing state from a parent down to the portalled text input is crazy slow
1 1
Ricky
What I mean is you can create a custom native component, mount it natively wherever you want it, and just pass props to it
2 1
Samuel
@samuel.fm
(fr though thank you will look into it!)
1 1
Ricky
I think the problem is there isn’t really a generic way to do it that will work in all RN apps, maybe it could work for an app that uses all full screen RN views with JS driven routing, but as soon as you’re embedding inside an app with native navigation it gets tricky
1 1
Ricky
There are also existing solutions to common problems you use portals for in DOM, for example dialogs and bottom sheets. For those use cases you can assist use the built in platform components for those, which libraries already do for you
1 1
Ricky
The Modal core component is basically a portal, but it doesn’t work for every use case, which is kinda my point above
1 1
Samuel
yeah we use our shitty portal component for our custom native bottom sheets but it’s subpar. we should definitely investigate doing the portal part natively
1 1
Nanniii
let me know if you can how it goes if you try, curious to know if you find issues. We never had any issues as far as i know but maybe just not caught or reported :)