fix: flashlist inverted handling #49
Merged
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
Highlights: - Fixed FlashList inverted handling since it was refactored in v2
e-younan
referenced
this pull request
Sep 17, 2025
* chore: added test screen to test issue #44 Highlights: - Added new test screen with the example code from issue #44 (#44) - Could not reproduce the issue with the TouchableOpacity not being pressable * feat: add new arch/expo 54 support Highlights: - Added new arch support - Fixed example project to work with Expo 54 * chore: add new arch support to docs Highlights: - Added version matrix to docs - Added note about new arch support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 changes introduces a fix for FlashList inverted handling since it was refactored in v2.
Motivation and Context
@ythomop pointed out that the new implementation was using the deprecated field. Thank you!
How Has This Been Tested?
Refactored the inverted example in the
exampleapplication to make use of this new prop.Types of changes
Checklist: