meliorence / meliorence/react-native-snap-carousel
Access snapToNext and snapToPrev inside renderItem.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.5k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
Is this a bug report, a feature request, or a question?
Question
I want to know if i can access those functions inside my renderItem using useRef;
const MyCarousel = () => {
const carouselRef = useRef(null);
...
const onPrev = useCallback(() => {
if (carouselRef && carouselRef.current) {
carouselRef.current.snapToPrev();
}
}, [carouselRef]);
const onNext = useCallback(() => {
if (carouselRef && carouselRef.current) {
carouselRef.current.snapToNext();
}
}, [carouselRef]);
...
const renderItem = useCallback(
({ item, index }) => {
return (
<>
<SwitchersContainer>
<Switcher onPress={onPrev)} />
...
<Switcher onPress={onNext} />
</DaySwitchersContainer>
</>
);
},
[onNext, onPrev],
);
...
return (
<Carousel<string>
ref={carouselRef}
...
renderItem={renderItem}
...
/>
);
}
This solution is not working, but if I take of the switcher from renderItem it works!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Carousel ref API and the renderItem callback shown in the issue, then reproduce the useRef behavior with the Switcher controls inside renderItem. Compare it with the working case where the switchers are outside renderItem; done means the supported behavior and required change or limitation are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100