This repository has been archived by the owner on Dec 15, 2018. It is now read-only.
Major improvements
<Link>
now respects modifier keys!<Link>
now accepts either a string or an object like so:
{
pathname: '/yo/this/is/a/url',
query: {
some: 'stuff'
}
}
<Link>
comes in two flavors now:<Link>
(old behavior) and<PersistentQueryLink>
(persists the previous query string unless thehref
prop provides one). Since you'll probably just use one or the other, this is a nice pattern:
import { PersistentQueryLink as Link } from 'redux-little-router';
- Query string support is fixed across the board!
- Added a util that sets up initial state on a server-side render. This correctly sets up query strings on the initial location dispatch.
- The
history
listener now lives in the store enhancer. The middleware no longer lives in the enhancer and must be used separately due to middleware order issues. - The store enhancer's reducer enhancer (enhance!!!) now supports
redux-loop
. - The current route info now lives at the top of the
router
state tree like it always should've (no morerouter.current
). You can still access the previous route onrouter.previous
. - New
Fragment
component that shows or hides children based on active routes (and even conditions of those active routes). - New
provideRouter
adds the router context to a top-level component. This means that<Link>
no longer requires you to pass indispatch
andhistory
(THANK GOD).