-
Notifications
You must be signed in to change notification settings - Fork 24.2k
-
Notifications
You must be signed in to change notification settings - Fork 24.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VirtualizedSectionList not exposed ? #20768
Labels
Ran Commands
One of our bots successfully processed a command.
Resolution: Locked
This issue was locked by the bot.
Comments
We are automatically closing this issue because it does not appear to follow any of the provided issue templates. Please make use of the bug report template to let us know about a reproducible bug or regression in the core React Native library. If you'd like to propose a change or discuss a feature request, there is a repository dedicated to Discussions and Proposals you may use for this purpose. |
react-native-bot
added
Ran Commands
One of our bots successfully processed a command.
📋No Template
labels
Aug 21, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Ran Commands
One of our bots successfully processed a command.
Resolution: Locked
This issue was locked by the bot.
Hello,
I just want to understand why
VirtualizedSectionList
is not exposed ?SectionList
inherit from it and is exposed, so I'm a little bit confused...I need this class because my datas are immutable, so I need to specify the getItem props, to handle this kind of data, something that isn't possible with
SectionList
if I'm right.EDIT: After a bit of reading of the code, I saw that
getItem
is override inVirtualizedSectionList
, to follow the same logic as withVirtualizedList
,getItem
should be specify inSectionList
, to allow the same behaviour as excepted when we useVirtualizedList
with immutable datas.The text was updated successfully, but these errors were encountered: