callstack / callstack/react-native-pager-view
Does not work within a ScrollView, bad performance when rendering multiple list components with real time data
- Langage dominant
- TypeScript
- Étoiles
- 3.4k
- Forks
- 476
- Merge moyen
- 10 j 21 h
- PR mergées (30 j)
- 2
Description
## Environment
react-native @ 0.79.1
react-native-pager-view @ 6.7.1
## Description
Since @MrRefactor requested a new issue to be created (https://github.com/callstack/react-native-pager-view/issues/784), here it is. Compared to version `7.0.0.rc0`, the current implementation performs much worse, especially in the case of a pager with multiple list components that have many rows and real-time data updates within. Also, the ScrollView bug persists, we are still not able to scroll a ScrollView when a Pager is rendered inside of it unless we perform the scroll gesture outside of the pager. I don't understand why support for the ScrollView based implementation was dropped as it performed perfectly well and IMO it should replace the current one. Honestly, based on the many threads and reports about this bug, I feel like this issue is being neglected.
## Reproducible Demo
```
import React from 'react';
import { ScrollView, StyleSheet, View, Text } from 'react-native';
import PagerView from 'react-native-pager-view';
const MyPager = () => {
return (
First page
Second page
);
};
const styles = StyleSheet.create({
pagerView: {
flex: 1,
},
});
export default MyPager;
```
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par l’exemple reproductible de MyPager dans l’issue, avec React Native 0.79.1 et react-native-pager-view 6.7.1. Étudiez les cas de PagerView dans ScrollView et de mise à jour en temps réel de plusieurs listes ; le travail est considéré comme terminé lorsque le ScrollView parent peut défiler quand le geste commence au-dessus du pager et que les performances du rendu sont améliorées.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- react-native
- Domaine
- mobile, performance
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100