You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 26, 2018. It is now read-only.
Provide your own reducer function that will receive actions of type LOCATION_CHANGE and return the payload merged into state.
This isn't enough information, and the user needs to look through the source code to understand where to actually put the data.
Can we change this to something like
Provide your own reducer function that will receive actions of type LOCATION_CHANGE and return the payload merged into the locationBeforeTransitions property of the routing state. e.g. state.set("routing", {locationBeforeTransitions: action.payload}).
The text was updated successfully, but these errors were encountered:
1. It was easier for me to think of the reducer by first knowing where
the state was expected to be. Writing it the other way around was
confusing
2. Add that the action payload data must go into the
`locationBeforeTransitions` property
reactjs#415
1. It was easier for me to think of the reducer by first knowing where
the state was expected to be. Writing it the other way around was
confusing
2. Add that the action payload data must go into the
`locationBeforeTransitions` property
#415
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the readme, it says
This isn't enough information, and the user needs to look through the source code to understand where to actually put the data.
Can we change this to something like
locationBeforeTransitions
property of the routing state. e.g.state.set("routing", {locationBeforeTransitions: action.payload})
.The text was updated successfully, but these errors were encountered: