-
Notifications
You must be signed in to change notification settings - Fork 642
Get devtools working #73
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -55,12 +55,26 @@ function update(state=initialState, { type, payload }) { | |
// Syncing | ||
|
||
function locationsAreEqual(a, b) { | ||
return a.path === b.path && deepEqual(a.state, b.state); | ||
return a != null && b != null && a.path === b.path && deepEqual(a.state, b.state); | ||
} | ||
|
||
function syncReduxAndRouter(history, store, selectRouterState = SELECT_STATE) { | ||
const getRouterState = () => selectRouterState(store.getState()); | ||
let lastChangeId = 0; | ||
|
||
// Because we're not able to set the initial path in `initialState` we need a | ||
// "hack" to get "Revert" in Redux DevTools to work. We solve this by keeping | ||
// the first route so we can revert to this route when the initial state is | ||
// replayed to reset the state. Basically, we treat the first route as our | ||
// initial state. | ||
let firstRoute = undefined; | ||
|
||
// To properly handle store updates we need to track the last route. This | ||
// route contains a `changeId` which is updated on every `pushPath` and | ||
// `replacePath`. If this id changes we always trigger a history update. | ||
// However, if the id does not change, we check if the location has changed, | ||
// and if it is we trigger a history update. (If these are out of sync it's | ||
// likely because of React DevTools.) | ||
let lastRoute = undefined; | ||
|
||
if(!getRouterState()) { | ||
throw new Error( | ||
|
@@ -75,6 +89,10 @@ function syncReduxAndRouter(history, store, selectRouterState = SELECT_STATE) { | |
state: location.state | ||
}; | ||
|
||
if (firstRoute === undefined) { | ||
firstRoute = route; | ||
} | ||
|
||
// Avoid dispatching an action if the store is already up-to-date, | ||
// even if `history` wouldn't do anything if the location is the same | ||
if(locationsAreEqual(getRouterState(), route)) return; | ||
|
@@ -87,14 +105,22 @@ function syncReduxAndRouter(history, store, selectRouterState = SELECT_STATE) { | |
}); | ||
|
||
const unsubscribeStore = store.subscribe(() => { | ||
const routing = getRouterState(); | ||
let routing = getRouterState(); | ||
|
||
// Only update the router once per `pushPath` call. This is | ||
// indicated by the `changeId` state; when that number changes, we | ||
// should update the history. | ||
if(lastChangeId === routing.changeId) return; | ||
// Treat `firstRoute` as our `initialState` | ||
if(routing === initialState) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll merge this like it is, but I would like to keep thinking about this. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Agreed. It's by no means optimal, it was just the easiest way I could get devtools to work as expected :/ The problem is of course that we can't read the initial location synchronously at the beginning. |
||
routing = firstRoute; | ||
} | ||
|
||
// Only trigger history update is this is a new change or the location | ||
// has changed. | ||
if(lastRoute !== undefined && | ||
lastRoute.changeId === routing.changeId && | ||
locationsAreEqual(lastRoute, routing)) { | ||
return; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd really prefer to avoid early returns. I'm fine merging this and changing it after if you want, but generally it makes the code flow clearer to avoid them. |
||
} | ||
|
||
lastChangeId = routing.changeId; | ||
lastRoute = routing; | ||
|
||
const method = routing.replace ? 'replaceState' : 'pushState'; | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remove this dev dependency? It should only be a dependency in the examples.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I rely on redux-devtools in the tests to ensure things work as expected, otherwise
reset
is difficult to test (kimjoar@4091b1e#diff-413f2628e9c93c46cec6db202ddb8ea4R165). If we only dispatch the initial state as payload it will become a new object and won't be=== initialState
(kimjoar@fb1508c#diff-1fdf421c05c1140f6d71444ea2b27638R111)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can of course deep-equal check with initial state instead. Then we could remove devtools as a dep
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooh right, I forgot about the tests. I don't really understand those tests (haven't dug into how the devtools works), but it seems cool to me to do that.