-
Notifications
You must be signed in to change notification settings - Fork 79
chore(section-list): use FlatList for SectionList #1187
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
base: master
Are you sure you want to change the base?
Conversation
Update demo `add-styles` behavior to reduce re-renders. [Asana](https://app.asana.com/1/47184964732898/project/1205761271270033/task/1210514672776456?focus=true)
Performing an update action (append, prepend, replace, replace-inner) with a delay requires that the behavior element has an id. The `basic-forms` demo was missing an id so was non functional. - Added an error to warn developers of this condition - Fixed the demo by adding an id to the element | Before | Error | After | | -- | -- | -- | |  |  |  | [Asana](https://app.asana.com/1/47184964732898/project/1204008699308084/task/1210535376481469?focus=true)
The previous functionality was returning zero if the `scroll-to-input-offset` attribute was missing, otherwise it was returning the default value (120). There was no path which returned the value of `scroll-to-input-offset` if available. - Created a new demo "Scroll to Input Offset" - Corrected the value return - Fixed a few typos in the demo and documentation | Before | After | | -- | -- | |  |  | [Asana](https://app.asana.com/1/47184964732898/project/1204008699308084/task/1210525849054931?focus=true)
524f6cd to
f4361f2
Compare
flochtililoch
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see a difference in behavior between the two implementation: the sticky header pushed the previous one with SectionList, while it overlap with the previous one with FlatList. Is this something we can fine tune?
I see the same "push up" animation in my clean react-native testbed. I'm not sure if the difference here is related to:
I'll poke around some more and see if I can get them to match. flatlist-demo.mp4 |
Example of using a react-native
FlatListin place ofSectionListfor ourhv-section-listcomponent.All functionality is retained. Code was able to be simplified especially around the scrolling behaviors.
Asana