Suggestion: previous location and params

It would be great to have the previous location and params inside *@asyncConnect* to know whether to update some specific part of the page or not. I have a quite complex page with multiple different sections that receive data from different API endpoints that may need to refresh when specific query string parameters change.

My current solution is to store the query (or whatever else I need from *location*) in a Redux store. Does anyone know of a better way to do it? I saw *reloadOnPropsChange* but it only works on a global level.

Start by reading the asyncConnect API and the reloadOnPropsChange behavior mentioned in the issue. Determine how previous location and query parameters should be exposed and how section-specific refresh decisions should work. Done means the behavior is specified and implemented with coverage for changes to relevant location parameters.

Written by the indexing model from the issue text.