feat!: expose library compatibilityFlags with new flag regarding header implementation
#2411
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
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.
Description
This PR introduces new
compatiblityFlagsobject to the library public API.It is meant as a source of truth for the library consumers (especially
react-navigation) to allow them to adjust to breaking changesdone in this library.
I've decided to go with single object with fields instead of individual constants, because it makes it easier for handling,
we don't have to change public exports every time we add something, it makes it easier to add/remove a flag.
Changes
compatiblityFlagsobject,usesHeaderFlexboxImplementation,Test code and steps to reproduce
N/A
Checklist