Open cem2ran opened 6 years ago
Yes. That's an actual issue. We want to have intermediate step to convert JS navigation screen props to Reason component which accepts props as function arguments instead of object. I don't know how to solve this issue right now. Maybe some escape with JS HoC accepting Reason component. I'm not sure when I'll have time to check this.
Currently it seems that intermediary
screen
components are created due to the screen parameter in routes being interpreted as a react functional component.This issue triggers the following warning and breaks the ability to navigate across navigators:
You should only render one navigator explicitly in your app, and other navigators should by rendered by including them in that navigator. Full details at:
https://reactnavigation.org/docs/common-mistakes.html#explicitly-rendering-more-than-one-navigator