Dispatching an action makes react-router-redux change router props -


i'm witnessing behavior fail understand , not seems right.

when dispatch action, components re-render because this.props.location (and others, params or routeparams) changes, , when "changes", mean pointer different, inner properties same.

the dispatched action not change route in way, data in redux store (on it's own mounted key).

consequently, shouldcomponentupdate (not overridden) detects change , forces re-rendering. there no change @ all!

that's annoying because have setinterval routine dispatches action call server every 30 seconds fetch data. , yet, connected components not care state change still re-rendered. redux panel shows action dispatched, no location_change.

if unplug react-router-redux (removing use of synchistorywithstore), behavior stops.

is expected behavior, or did miss something? i'd not have override shouldcomponentupdate in of connected components.

could point me react router props being injected in components?


Comments

Popular posts from this blog

sequelize.js - Sequelize group by with association includes id -

android - Robolectric "INTERNET permission is required" -

java - Android raising EPERM (Operation not permitted) when attempting to send UDP packet after network connection -