Pure-redux-router-link NPM

pure-redux-router-link

A simple but effective <Link /> component for pure-redux-router (better for SEO rather than dispatching yourself)

Installation

yarn add pure-redux-router-link

Usage

import Link from 'pure-redux-router-link'

// as a standard href path string:
<Link href='/list/db-graphql'>DB & GRAPHQL</Link>

// as an array of path segments:
<Link href={['list', 'react-redux']}>REACT & REDUX</Link>

// as an action object:
<Link href={{ type: 'LIST', payload: { category: 'fp' } }}>FP</Link>

In all 3 cases, a simple link will be rendered, eg:

<a href='/list/fp'>FP</a>

Recommendation

Creating your links with hrefs as an action object is obviously the best solution, as it will allow you to change static path segments in the routesMap you pass to connectRoutes() at any time, without having to change any of your <Link /> components. That means you only have to change URLs in one place.

For example, if you have:

import { createStore, compose, applyMiddleware, combineReducers } from 'redux'
import createBrowserHistory from 'history/createBrowserHistory'
import connectRoutes from 'pure-redux-router'

const history = createBrowserHistory()

const { enhancer, middleware, reducer } = connectRoutes(history, {
  LIST: '/list/:category'
})

const rootReducer = combineReducers({ location: reducer })
const store = createStore(rootReducer, compose(enhancer, applyMiddleware(middleware)))

Then you can change the static segment of the path at any time, eg:

const { middleware, enhancer, reducer } = connectRoutes(history, {
  LIST: '/browse/:category'
})

But its entirely up to you. If it's easier to start to thinking in terms of paths, go for it! If that's the case, we recommend the array syntax, since its easier to pass variables, eg:

const category = 'react-redux'
const href = ['list', category]
<Link href={href}>REACT & REDUX</Link>

const category = 'react-redux'
const href = `/list/${category}` // can get long & yucky with lots of variables
<Link href={href}>REACT & REDUX</Link>

Additional Props:

down: boolean = false - if true supplied, will trigger linking/dispatching onMouseDown instead of onMouseUp
shouldDispatch: boolean = true - if false will not dispatch (useful for SEO when action handled elsewhere)
target: string - eg: '_blank' to open up URL in a new tab (same as standard target attribute to <a> tags)
onPress: (SyntheticEvent) => ?boolean - you can provide an onPress handler to do anything you want (e.g. play a sound), but if you return false it will prevent linking/dispatching just as you may be used to. TIP: Use returning false instead of shouldDispatch when you want to dynamically determine whether to trigger the action or not!
...props: - you can pass any additional props that an <a> tag takes, such as className