@zohodesk/router-middleware
v1.0.0-beta.28
Published
1. History object is a side-effect. If you are using redux then handle history object inside middleware. Don't flow over component. In react-router, histroy object flow over component via context. All Link(withRouter) component more couple with router. I
Downloads
957
Maintainers
Keywords
Readme
react-router-redux
##Just my thought.
- History object is a side-effect. If you are using redux then handle history object inside middleware. Don't flow over component. In react-router, histroy object flow over component via context. All Link(withRouter) component more couple with router. It breaks some reusablity.
- Connect(React-Redux) has subscriber model for state changes UI changes. If we sync URL state into app state then we may use same connect component for URL changes also.
I tried some example
npm install
npm run example
http://localhost:9090
1.0.0-beta.16
Match - props support array name={['page1','page2']}
1.0.0-beta.21
reject added
1.0.0-beta.22
1.0.0-beta.25
URL block reason key added in redux state
1.0.0-beta.26
Added support to allow action while url changing
1.0.0-beta.27
Added catch block to allow route change irrespective of the error occured while url is changing.
1.0.0-beta.28
Dispatch Previous Routing state while changing to new Routing state.