leecade / leecade/react-native-swiper
Can't able to disable infinite scroll
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.5k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
Which OS ?
ios
Version
Which versions are you using:
10.14.6
- react-native-swiper v? 1.6@nightly.5
- react-native v0.?.? 0.61.5
Expected behavior
I have designed a vertical scroll for my screen, my expected behavior is not having the dotPagination Indicator, scroll shouldn't be enabled on the 0th index screen, but when a button clicks it scrolls to page 2 (index 2) when the page scrolled to page 2 the scroll should be enabled at that time when user scrolls up again the scroll needs to get disabled again (we should only use the button to go to page 2 from the page 1)
Actual behavior
I have disabled the scroll in the first screen and adds scroll on click the button, but when I swipe page 2 downside again for 0.5 sec it loads the first screen and again coming back to the second screen also the behavior of the first screen is applied to second screen this time (this shouldn't happen), =====> In Short (swipe scroll should be in the second screen, button scroll should be in the first screen) ==>Better to disable down swipe in the second screen, because when I swipe up to the first screen it works fine, the page stays there and scroll is disabled too
How to reproduce it>
To help us, please fork this component, modify one example in an example folder to reproduce your issue and include the link here.
- Find my code here - https://sharemycode.fr/z02
I have tried couple of props and control functions given by the swiper still nothing helped me achieving this
Note: I'm using react-native hooks
Contributor guide
No contributing guide indexed for this repository
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 linked reproduction and compare its behavior with the issue's expected and actual behavior. Review the swiper props and control functions used there, then verify that button navigation reaches page 2 while the intended swipe directions are enabled or disabled on each page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100