feat: ✨ introduce separate package for navigation integration #152
Conversation
This file contains 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
okwasniewski
force-pushed
the
feat/separate-package
branch
6 times, most recently
from
6df0270 to
5a56be3
Compare
okwasniewski
force-pushed
the
feat/separate-package
branch
from
5a56be3 to
4b0165d
Compare
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.
PR Description
This PR introduces separate package for React Navigation integration, namely:
@bottom-tabs/react-navigation.In the next release (after releasing the package) we will drop support for React Navigation v6 allowing users to stay on lower version of
@bottom-tabs/react-navigationif they want to continue using React Navigation v6.How to test?
CI Green
Screenshots
N/A