Doesn't work when there is nested `portals.OutPoral` about react-reverse-portal HOT 6 OPEN

Woah, ok. Even passing children to OutPortal is pretty unusual, let alone trying to nest that! I can see how this might be useful for these kinds of provider use cases, but it's difficult to think through exactly how this should work. I'm not aware of any good reason why this wouldn't work, but I've never tested it before myself.

That said, I'd be happy to support this if it's possible to do so without adding too much extra complexity or breaking anything else.

Do you want to look into it? If you can just work out why it doesn't work already then that'd be very useful, and if you want to open a PR to fix it that'd be even better.

from react-reverse-portal.

Thanks for so quick reply @pimterry , actually before opening this issue I've tried to understand the code myself already, but there was no luck cause I'm still a noob lol. However let me try for several extra hours, if I still can't figure it out, perhaps I will need your need. Thanks.

from react-reverse-portal.

Hmm it seems because the original design didn't expect OutPortal to have children in mind from the first place (as you stated above).

Instead of

App
  InPortal
    Constate
      useColor.Provider
  InPortal
    Constate
      useCounter.Provider
  OutPortal // for InPortal>Constate>useColor.Provider
    div
      OutPortal // for InPortal>Constate>useCounter.Provider
        div
          button
          Counter
            ...

here it is the actual component tree

so the behavior instead of replacing OutPortal with InPortal, it brings all props (including children) from OutPortal to InPortal.

Just an update to you, I'll diagnose closer the code.

from react-reverse-portal.

Hi @loia5tqd001 did you make any more progress here? Let me know if there's anything I can do to help.

from react-reverse-portal.

Hi @pimterry I really have no idea how to tweak the package to make it work for this use case 🤥 like I don't even know which question to ask, otherwise I asked already

from react-reverse-portal.

Ok, fair enough. Yes, this use case isn't a priority for me right now, or for normal usage in general I think, but I would like to support it in future if possible. I don't think there's anything that would make this impossible, it's just a bit difficult to work out the details.

If you or anybody else does work out the underlying issue here and put a PR together to fix it, I'd be very happy to look at that. I'll leave this open for now.

from react-reverse-portal.