More robust way to handle top-level navigator differences - Githubissues

react-navigation / rfcs

RFCs for changes to React Navigation

Other

88 stars 16 forks source link

More robust way to handle top-level navigator differences #56

Open brentvatne opened 6 years ago

brentvatne commented 6 years ago

giacomocerquone commented 5 years ago

A bit of more context here? As stated in this my other comment (https://github.com/react-navigation/react-navigation/issues/4490#issuecomment-519468407), I'd like to know why this happens. Exactly why the reference is set after the navigator (and its screens) are rendered