leecade / leecade/react-native-swiper
[DISCUSS] Fork or cleanup this package? Nominate PRs proven useful to you for merging
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.5k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
Issues and PRs are largely unattended for months now, and the owner just updates README with recruitment ads. My app's main navigation is built around this library so I have a vested interest in improving and maintaining this, with community contribution and merging useful PRs on queue here. My own fork is working well up to current RN 0.57.0 on both iOS and Android.
If we move to a new repo under a new name, what name should it be? What PRs should be merged?
My idea for new name: react-native-snap-scrollview or react-native-snap-swiper
Discuss.
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
Begin by reviewing the react-native-swiper repository, its open PR queue, and the linked community fork, which targets React Native 0.57.0 on iOS and Android. The issue does not name implementation files, tests, or a defined change; completion would require an agreed repository direction, selected PRs, and a maintenance plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100