You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then fetch a single modelB, that contains a modelA (nested in the result), like getState('modelB.byId', { id: 123 }). The store will be updated to look like this:
The cid values no longer match. The byId and byCid reducers seem to stay in sync, but the find reducer has a different value.
It might actually be that the getState.byId call is made first followed by the getState.byCid call though...either way, this seems to be happening.
Side effects appear to include React issuing a warning about duplicate keys when it occurs (when rendering a list of items), though it won't render the duplicate items.
The text was updated successfully, but these errors were encountered:
The follow appears to be true (though the order might be reversed, need to debug more):
If you make an api request using
getState('modelA.find')
, the data in the store might look like this:Then fetch a single modelB, that contains a modelA (nested in the result), like
getState('modelB.byId', { id: 123 })
. The store will be updated to look like this:The
cid
values no longer match. ThebyId
andbyCid
reducers seem to stay in sync, but thefind
reducer has a different value.It might actually be that the
getState.byId
call is made first followed by thegetState.byCid
call though...either way, this seems to be happening.Side effects appear to include React issuing a warning about duplicate keys when it occurs (when rendering a list of items), though it won't render the duplicate items.
The text was updated successfully, but these errors were encountered: