Feature Request: Inject navigation in tree about native-navigation HOT 2 CLOSED

This could possibly also indirectly fix the dependency on React mentioned here #54 (comment)

I think there is a bit of misunderstanding here: React dependency mentioned in #54 is a native dependency. Current implementation assumes that React is a framework that Swift can import using import React. I think these issues are not related.

from native-navigation.

Indeed this issues are not related.

@dzannotti have you seen the Integrating with Redux guide?

I have never felt any pain with adding redux or context-based top level elements to my app using native navigation's approach, so i'm not convinced that this being a real issue.

In your example, what component is rendering <Provider> here? Where is that component being mounted and rendered? What is it being rendered into?

Native navigation renders each screen into their own RCTRootView, and this may fundamentally go at odds with what you are proposing.

I hope that makes sense. Let me know if I'm not being clear.

from native-navigation.