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
Question: calling navigate on top level component #71
Comments
The following should work. If it doesn't then it is probably a bug. If it does work, can you find a good place to add this to the documentation?
|
works, thanks. i'll try to add a doc for it! |
time to give back, PR - #122 |
Hey @ericvicenti @kelset @brentvatne How can this be done if the logic that does the dispatch is in another component that is rendered after the navigator on the same level? In my case I create my navigators (A drawer with a stack navigator and other nested navigators) and then I render them using the Drawer + PushController rendering
PushController snippet:
|
hey @rtman - if you believe there is a bug please create an issue and follow the template. otherwise try one of the support options from https://reactnavigation.org/ :) |
@brentvatne Ok, I didn't think it was a bug, so I opted to ask on stack overflow. If anyone is inclined to help me out here it is: https://stackoverflow.com/questions/48719141/how-to-call-navigate-from-a-component-rendered-at-top-level |
@ericvicenti AppNavigation.js
ReduxNavigation.js
App.js
|
assume we have this component.
how can i trigger navigate event from the top level of
App
component?in this example lets say under
someEvent
function.this event is for top level (like new push notification arrived) and not per each individual loaded screen so it has to happen in
App
class.The text was updated successfully, but these errors were encountered: