plan to support state object.

[seokgyo]

history.pushState() takes a state object as first parameter and Link tag takes it as a property. It looks like redux-simple-router do not support this state object yet.
Do you have a plan to support this?

[jlongster]

Hadn't thought about it much, but yep, we definitely could add it as a parameter in the updatePath parameter, store it in redux and then pass it to pushState. Only thing to be careful is to make sure it's a serializable thing, but it probably is.

[ryanflorence]

We're going to be adding push and replace (instead of pushState and replaceState) to History, the signature will be:

push(path, state)
replace(path, state)

Seems like you can just say your API, could get your API ready by adding those two actions as well with the same signature.

[jlongster]

@ryanflorence thanks. I'm not sure how I feel about just a push and replace action; seeing those actions in the wild don't really describe what they do (but as methods on history is totally makes sense). Maybe pushRoute and replaceRoute, or pushPath and replacePath?

[jlongster]

Let's move the discussion for state here: #38