WIP feat(ios): add useLegacy flag #763
Closed
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
previously approved these changes
Aug 31, 2023
| @@ -0,0 +1,8 @@ | |||
| <?xml version="1.0" encoding="UTF-8"?> | |||
| pageMargin={10} | ||
| // Lib does not support dynamically orientation change | ||
| orientation="horizontal" | ||
| useLegacy={true} |
There was a problem hiding this comment.
You can specify just useLegacy without passing true
|
Spacing issue |
added 2 commits
August 31, 2023 20:17
Closed
troZee
changed the title
3 tasks
|
Closed in favor of #783 |
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.
Summary
useLegacyflag as a fallback to a legacy component (UIPageViewController)RNCScrollViewPagerto don't introduce any breaking changes for expo golegacydir in theiosfolderTest Plan
Compatibility
Checklist
README.md