Releases: cher-ami/router
Releases · cher-ami/router
v3.6.1
Full Changelog: v3.6.0...v3.6.1
Update version for npm
v3.6.0
What's Changed
- Fix subrouter for parent staticprops by @pierregradelet in #166
- Allow to use
<div>instead of<main>on Stack by addingasprop
Full Changelog: v3.5.5...v3.6.0
v3.5.5
v3.5.4
What's Changed
- Fix server-side function extractQueryParamsAndHash by @cherami-tech in #164
Full Changelog: v3.5.3...v3.5.4
v3.5.3
What's Changed
- Add hash example by @cherami-tech in #162
- Fix queryparams hash history by @cherami-tech in #163
- Replace Stack tag by @theoplawinski in #160
New Contributors
- @theoplawinski made their first contribution in #160
Full Changelog: v3.5.2...v3.5.3
v3.5.2
Fix langServide to handle hashHistory :
- Added
isHashHistoryprops to<Router>and toLangServiceoption - Added test on
getRouteFromUrlishashHistoryis used
v3.5.1
Patch for default props deprecated warning
v3.5.0
Re implement getPaused and setPaused because history block API don't keep the last URL pushed in history.
v3.4.0
-
remove
getPausedandsetPausedbecause history block API can do it. #149 -
props route returns queryParams & hash #153
export type TRouteProps = { params?: TParams queryParams?: TQueryParams hash?: string [x: string]: any }
v3.3.0
Fix sub-router createUrl #154
When with createUrl of a sub-router, from a sub-router, the URL wasn't build properly on the server-side. This cause a diff of render between server and client.
To resolve this issue we need to:
- Get an "is root router" state on server and client side
- Harly reset all Routers property on each http request (because the nodejs runtime is not clear on each http request)
- Rework
createUrl()function: internalize all thegetUrlByRouteNamelogic - Update and split tests
- Remove old core
getUrlByRouteName()&getFullPathByPath() - Remove core
compileUrl(), use path-to-regexpcompileinstead