Combine AppContainerFunctor and AppContainer again, get example to run. #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MoOx
approved these changes
Sep 30, 2019
|
And for 2 (moving example) that can be a nice idea as we could make this a react native template so people can start with that! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I combined AppContainerFunctor and AppContainer again. This is less awkward, and if not using the functor, usage will still be zero-cost as the file won't be imported.
I updated the example so that the Reason code builds at least. However, using
yarn link, I couldn't get Metro to find@reason-react-native/navigation. I think the simplest solution would be to move the example to another repo@reason-react-native/navigation-example.