Releases: STRML/react-router-component
Releases · STRML/react-router-component
0.36.3
0.36.2
0.36.1
0.36.0
- Router: Avoid unnecessary
setPath()calls when receiving identical props. Fixes #177 - CaptureClicks: Potentially breaking change:
- Previously,
<CaptureClicks>would callprops.gotoURL()(default:window.location.href = e.href) as soon
as the first router failed to match. This was error-prone as it depended on the registration order of routers.
Subrouters with limited routes could cause navigation not to occur.- This was masked somewhat by the extraenous
setPath()calls. Navigation would occur, butonNavigationwould
not fire.
- This was masked somewhat by the extraenous
- Now,
<CaptureClicks>callsprops.gotoURL()only if all routers fail to match.
- Previously,
0.35.0
0.34.0
0.33.0
- Possibly breaking changes to callbacks:
onNavigationandonBeforeNavigationis now called on all routers.- This fixes #95
- Arity change in callbacks: now
(path, navigation, match)from(path, navigation).- The trailing
matchparameter was added to better track subrouter matches. navigationwill no longer contain amatchattribute, which was a singleton and thus
could not be unique when using multiple routers.
- The trailing