Closed nmassey closed 2 months ago
Latest commit: 00c948bca03ab1aeeaff97e5f077b1b4cd61e2e4
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
react-native-reanimated-carousel | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Sep 15, 2024 4:46am |
A potential alternative solution -
Something like ...props
on PaginationItem
and forwarded to its child (e.g. <View {...props}>
or <Animated.View {...props}>
) might work (see StackOverflow here: https://stackoverflow.com/a/68952082 ). But this feels a little clunkier to me.
Overview of the bug
As per #676, v4.0.0-canary.13 accidentally introduced a bug that caused the click events on
Pagination.Basic
to no longer work.This appears to have been accidentally introduced in #655
Thanks to @qwertychouskie for reporting here:
676
Why
From the TouchableWithoutFeedback docs:
What: the fix
Pagination.Custom
, standardize by importingTouchableWithoutFeedback
fromreact-native
(like we already do forPagination.Basic
)Pagination.Basic
andPagination.Custom
, lower the<TouchableWithoutFeedback>
wrapper to inside ofPaginationItem
so that it is immediately around the target<View>
(or<Animated.View>
) insteadWhy
When using
TouchableWithoutFeedback
, it's important to keep<TouchableWithoutFeedback>
immediately around the child<View>
component.Suggestion for reviewer
As a bulk of the changeset is just whitespace changes, I suggest reviewing this PR with whitespace hidden -