-
Notifications
You must be signed in to change notification settings - Fork 290
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
React Native 0.23.1 warning: 'In next release empty section headers will be rendered' #39
Comments
The full error message is: This flag is referenced in the documentation of the ListView. I'm not sure how @FaridSafi would like to solve the issue, but currently it is possible to mute the error passing it the flag, knowing that at some point the flag will be deprecated. Anyways @benvium, as a temporary fix insert the following line while calling GiftedListView: |
Thanks @jeromegrosse, that works, at least until the next version of React Native. |
in the next release, we're supposed to exclude the indices from the sectionID object: https://facebook.github.io/react-native/docs/listview.html#enableemptysections But what does that mean? Where will we exclude the indices? Where is the sectionID object? I don't see it in the source code. |
AFAIK, this is just a confusing way of saying that in the future if you don't want the headers for empty sections to show up, don't include that sectionId in the data blob you passed to https://github.com/facebook/react-native/blob/master/Libraries/CustomComponents/ListView/ListViewDataSource.js |
enableEmptySections={true} work for me, thanks #jeromegrosse |
…ySections` More details refers to: FaridSafi#39
I am using the new FlatList and passing that prop didn't work ... maybe it doesn't get pass later to the ListView component. So ... I commented the warning in the ListView.js file located in .../node_modules/react-native/Libraries/Lists/ListView/ListView.js line 433-437. It is not the best solution .. but we know the warning exists and it doesn't pops up anymore. I hope someone finds it useful. |
I did like @mgarc729 but clearly if there is better solution, I'm here ! |
Since upgrading I'm now getting this error.
My setup looks like this:
e.g. I'm using withSections={false}. Any ideas?
The text was updated successfully, but these errors were encountered: