-
Notifications
You must be signed in to change notification settings - Fork 72
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
InfiniteScroller console warning about unique key #562
Comments
1. Fixes oVirt#562 as per https://github.com/CassetteRocks/react-infinite-scroller/issues/133. Added `key={0}` to the loader and the InfiniteScroller warning went away. 2. Added an `all([])` wrapper around the rootSaga to resolve the deprecation warning. 3. Refactored `VmDetail/index.js` to add `key={0}` to the React.Fragment use as it was causing a warning similar to InfiniteScroller's warning.
1. Fixes oVirt#562 as per https://github.com/CassetteRocks/react-infinite-scroller/issues/133. Added `key={0}` to the loader and the InfiniteScroller warning went away. 2. Added an `all([])` wrapper around the rootSaga to resolve the deprecation warning. 3. Refactored `VmDetail/index.js` to add `key={0}` to the React.Fragment use as it was causing a warning similar to InfiniteScroller's warning.
1. Fixes oVirt#562 as per https://github.com/CassetteRocks/react-infinite-scroller/issues/133. Added `key={0}` to the loader and the InfiniteScroller warning went away. 2. Added an `all([])` wrapper around the rootSaga to resolve the deprecation warning. 3. Refactored `VmDetail/index.js` to add `key={0}` to the React.Fragment use as it was causing a warning similar to InfiniteScroller's warning.
1. Fixes oVirt#562 as per https://github.com/CassetteRocks/react-infinite-scroller/issues/133. Added `key={0}` to the loader and the InfiniteScroller warning went away. 2. Added an `all([])` wrapper around the rootSaga to resolve the deprecation warning. 3. Refactored `VmDetail/index.js` to add `key={0}` to the React.Fragment use as it was causing a warning similar to InfiniteScroller's warning.
Add key={0} to the loader fix it. see |
hello, i add key to infinite
and still have warning in console, someone can help me ? |
Yes I too have the same problem - I am using V1.2.4 |
Anybody still come out with the same issue? I use version 1.2.6 and there is still the same warning… |
I also have this issue with version |
If someone is facing this issue, make sure you wrap your component with a div and key: loader={
<div key={0}>
<MyLoaderComponent />
</div>
} I was having this warning as well because the key was inside my component, but moving it in the same place as the |
Console log shows
Works fine anyway, lower priority to make code clean.
The text was updated successfully, but these errors were encountered: