This repository has been archived by the owner on May 3, 2024. It is now read-only.
Releases: cellog/ion-router
Releases · cellog/ion-router
Release Version 0.9.0
Massive overhaul
- integration testing now guarantees proper sequencing of url/state binding
- added automatic resetting of state upon exiting a route (fully configurable)
- added more dynamic parent route management. Path is configured, but so are parameters on exiting a route
- routes are now added in batches. Every
<Router>
tag's contents is dispatched in a single action to the store, which will cut down on re-renders - routes are removed if the
<Router>
tag that defines them is removed from rendering. This makes custom sub-routes for large projects very easy to implement - many improvements due to ideas in #9 thanks to @alonbardavid
- internally, the RouteManager object was dropped in favor of a more functional/saga-based approach.
- added more awareness of server-side rendering (necessary with the batched change. A boolean is passed to the router setup function. It should be set to true in any environment where
componentDidMount
is not called, such as when rendered withrenderToString
Release Version 0.8.1 (alpha)
- Fix #9
Release Version 0.8.0 (alpha)
- add call of route parameter setting via exit route, customizable with exitParams
Release Version 0.7.2 (alpha)
- fix incorrect proptype for routes in Link tag
Release Version 0.7.1 (alpha)
- fix a minor React warning in Link tag
Release Version 0.7.0 (alpha)
- Add RouteToggle, a convenience toggle that triggers on route changes, but can be extended
- enhance matchedRoutes to accept an array of routes, which matches any by default, but can be extended
to strictly match all of them by passing true as the 3rd parameter
Release Version 0.6.2 (alpha)
- fix improper prop type warning for Toggle - was triggering 100% of the time because of a misunderstanding of how the propType validation is triggered
Release version 0.6.1 (alpha)
- both of the new features added in v0.6.0 would not work in a code splitting scenario. Now they pull in routing information from the redux store, where it is guaranteed to be correct
Release version 0.6.0 (alpha)
- implement the ability to
<Link route="routename" param1="something" ... />
so we can create abstract links to routes without having to explicitly state the internal paths - implement the ability to extend a route with the parent param, which will pull the route definition from the route and use that extend it.
Release version 0.5.0 (alpha)
This release adds the ability to debug whether a toggle is working or not.
It also adds smarter proptypes, if a componentMap is specified. It will use
the names of the components you pass in to validate the properties, instead
of the static names.