Track route transitions to support time travel debugging

One problem with this addon today is that route transitions are not kept in sync with redux. This quickly becomes a problem if you decide to bolt on time travel debugging and rewind/fast forward. I’m throwing this issue up to help track what’s required and how to approach it in ember.

• didTransition spike showing how simple it is to dispatch an event to redux with url and params
• verify travel backwards/forwards is supported by the default redux chrome extension
• unlock hot reloading to use in combination with time travel
• discuss if developers will prefer to ‘opt-in’ or if we should add this by default

[toranb]

I’ve been working with @MiguelMadero on a hot reloader for ember-cli and we’ve got a very basic proof of concept going now (90% of the hard work and brains behind it was Miguel)

Here is a quick demo to show it in action with ember-redux

[toranb]

I was able to spike this out with only 1 reducer and a few lines of code in the didTransition of the ember router itself (not terrible actually).

https://github.com/toranb/ember-redux-ddau-example/commit/76dfce3956a508724ed958142e2fe4bc85167d5a

The behavior is like you suggest - it will fire any async actions on the route you transition “back to” but in practice I found you can just toggle it off and continue going in rewind mode 😃

Here is what time travel looks like using the code above (seems identical to what I get with react-router-redux today.