dispatching the current route has no effect

[hedgepigdaniel]

This could be useful for example to scroll to a particular hash on the page (even if it is already in the URL)

Currently the transformAction middleware blocks actions that match the current route exactly, because req.isDoubleDispatch() is true.

[hedgepigdaniel]

Reproduceable with the boilerplate on the repro/scroll branch. Try using one of the section links in the sidebar. Then scroll away from that section, and notice that clicking on the same section link does not scroll back to it.

[Guria]

I also faced with this behavior. I tried to dispatch same action but with different state property set. Unfortunately rudy doesn't checks if state is different.

[hedgepigdaniel]

That's an interesting point about how it doesn't check for a different state in isDoubleDispatch. It probably should, so PR welcome.

That said, such a PR would have to choose a way of comparing the state. Browsers are meant to use the structured clone algorithm to serialize the state - so probably that would be a good way to compare it.