laszlokardinal/reduxen

Redux first router

reduxen

Reduxen extends Redux's functionality with routing. Provides a middleware that connects redux with the history api, and location (dispatches actions on changes, and calls history methods on incoming actions), and a reducer to keep the URL in sync with the state.

Why?

With reduxen you will be able to move the data fetching logic from the view to the data layer of your single page application, therefore the view can be pure, deterministic, and easily testable. The view's responsibility can be only producing the UI based on the state and propagating incoming events from the user, while the data management and business logic can entirely take place in the data layer.

You can create side-effects for the router's actions inside redux with sagas, epics or plain middlewares, as well as manipulate the history by dispatching router actions from them.

Packages

• reduxen: Core module, that integrates with redux
• reduxen-react-dom: React DOM bindings

reduxen's Issues

match() matches on the pattern "/posts/:id/*" with "/posts" path

The asterisk in match()'s pattern needs at least one part in the path to match

Intended to work as "zero or more"

Query parameter values don't get decoded

parseUrl parses invalid urls (e.g. "invalid" -> { path: "invalid" })

<Link /> throws exception when "to" prop is an invalid string (e.g. starts without /)

initialUrl gets parsed without decoding url encoded characters

<Link /> captures middle button clicks