Skip very first @@router/LOCATION_CHANGE

[rybon]

When starting the app, this dispatch is always fired:

{
    "type": "@@router/LOCATION_CHANGE",
    "payload": {
        "pathname": "/",
        "search": "",
        "hash": "",
        "state": null,
        "action": "POP",
        "key": null,
        "query": {},
        "$searchBase": {
            "search": "",
            "searchBase": ""
        }
    }
}

Is there a way to turn that off? I tried adjustUrlOnReplay: false, but I still see this dispatch happening. In a test environment I want the app to be inert, in other words not trigger a dispatch on its own, so I can feed it recorded dispatches later on. Is that possible?

[dlmr]

I believe this is related to #412.

I know what is causing it and actually have what I believe is a correct fix for it locally but I have not yet had time to write good enough tests as requested in #412. Maybe I should push it to PR so others can contribute and maybe help with the test aspects.

[slowsay]

you should be disposed combineReducers({function,function})

[rybon]

@dlmr feel free to publish your PR.

[dlmr]

@rybon I have pushed my PR as #445 but I think I misspoke unfortunately.

It is correct that a LOCATION_CHANGE is dispatched on initial render. The reason for this is because there currently is no other way for the store to be initialised with the correct information, that is the correct representation of the what the browser URL is and this will be different each time since history is using a random key to make the location unique.

[chrisabrams]

I wish this fired for me on page load. I have to make a page change before seeing this.

[dlmr]

@chrisabrams If you are using SSR the change in #445 will "fix" that.

[chrisabrams]

@dlmr got it; will look forward to the "fix"

[pipi32167]

Still have the same problem, not using SSR.

I use redux-devtools and redux-devtools-extension to debug, and find out the last action like this: