You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RFR had some docs on Native support. It contains some intentions to provide some updates on it, but it seems they are a bit outdated now.
Was RN support somehow transferred to rudy? Is there any usage examples?
The text was updated successfully, but these errors were encountered:
I personally haven't tried it yet, but I mean to. I don't imagine there would be a huge difference vs using it with RFR though.
My recommendations (based on my experience on an app using RFR) would be:
use https://github.com/react-navigation/redux-helpers to dispatch redux actions in response to input handled by react-navigation. Intercept these actions in mapDispatchToProps (which are not very specific, e.g. Navigation/NAVIGATE) and redispatch them as actions matching the intended structure of your app (e.g. SETTINGS_SCREEN).
write your own reducer to store the navigation state for each navigator. More work, but you'll understand whats going on and you can have those nice app specific actions.
make sure that the navigation actions are serializable to a URL, and dispatching one of them is enough to create a valid navigation state (that way universal linking shouldn't be difficult)
If your app's back button does not go back through a single linear stack, do not use rudy's back functionality (which only supports a single stack). Instead, handle your concept of "back" in your own reducers, and always go "forward" as far as rudy is concerned.
RFR had some docs on Native support. It contains some intentions to provide some updates on it, but it seems they are a bit outdated now.
Was RN support somehow transferred to
rudy
? Is there any usage examples?The text was updated successfully, but these errors were encountered: