@cerebral/router
Install
NPM
npm install @cerebral/router
Description
The router of Cerebral does not affect your view layer. A url change triggers a signal that puts your application in the correct state. Your view just reacts to this state, like any other state change.
Read more about the router in the Cerebral in depth - Routing article.
Instantiate
import { Controller, Module } from 'cerebral'
import Router from '@cerebral/router'
const router = Router({
routes: [
{
path: '/',
signal: 'app.homeRouted'
}
],
onlyHash: false,
baseUrl: null,
allowEscape: false,
preventAutostart: false
})
const app = Module({
modules: { router }
})
const controller = Controller(app)
getOrigin
function myAction({ router }) {
router.getOrigin()
}
getPath
function myAction({ router }) {
router.getPath()
}
getSignalUrl
Allows you to convert a signal to its corresponding url. This is useful when you actually want to produce the url for a hyperlink etc. To do this you need to create the router in its own file:
router.js
import Router from '@cerebral/router'
export default Router({
routes: [
{
path: '/items/:itemKey',
signal: 'items.itemRouted'
}
]
})
And attaching it to the controller:
controller.js
import { Controller } from 'cerebral'
import router from './modules/router'
import items from './modules/items'
export default Controller({
modules: { items, router }
})
You will be able to use the same router instance to produce url based on registered sequences:
import router from './router'
export default connect(
{
item: state`items.list.${props`itemKey`}`
},
function ListItem({ itemKey, item, itemRouted }) {
return (
<li key={itemKey}>
<a href={router.getSignalUrl('items.itemRouted', { itemKey })}>
{item.name}
</a>
</li>
)
}
)
getUrl
function myAction({ router }) {
router.getUrl()
}
getValues
function myAction({ router }) {
router.getValues()
}
goTo
action
function myAction({ router }) {
router.goTo('/items')
}
operator
import { goTo } from '@cerebral/router/operators'
export default [goTo('/items')]
operator with dynamic URL
import { state, string } from 'cerebral/tags'
import { goTo } from '@cerebral/router/operators'
export default [goTo(string`/${state`app.currentView`}`)]
redirect
action
function myAction({ router }) {
router.redirect('/items')
}
operator
import { redirect } from '@cerebral/router/operators'
export default [redirect('/items')]
operator with dynamic URL
import { state, string } from 'cerebral/tags'
import { redirect } from '@cerebral/router/operators'
export default [redirect(string`/${state`app.currentView`}`)]
redirectToSignal
action
function myAction({ router }) {
router.redirectToSignal('app.itemsRouted', { foo: 'bar' })
}
operator
import { redirectToSignal } from '@cerebral/router/operators'
export default [redirectToSignal('app.itemsRouted', props`payload`)]
reload
action
function myAction({ router }) {
router.reload()
}
operator
import { reload } from '@cerebral/router/operators'
export default [reload]
routes
import { Controller } from 'cerebral'
import Router from '@cerebral/router'
const controller = Controller({
modules: {
router: Router({
routes: [
{
path: '/',
signal: 'app.homeRouted'
},
{
path: '/projects/:projectId',
signal: 'app.projectRouted'
}
]
})
}
})
When a mapped signal triggers it will trigger with a payload if either params are defined on the route or the url has a query. For example /projects/123?showUser=true will produce the following payload to the signal, available on the props :
{
projectId: '123',
showUser: true
}
setUrl
function myAction({ router }) {
router.setUrl('/foo')
}
EXPERIMENTAL
We are currently working on functionality that allows you to bind urls to your state, also allowing you to create more complex relationships between your application state and the url. This API is very likely to change, but please feel free to try it out and give us feedback.
mapping
The map property let's you create a mapping between state and
url parameters. This works both ways: when you change the state,
it sets the url from state and when the url changes, it triggers
the state changes.
This automatic mapping is only active if the current url
is active. Note also that when you use state mapping, the 'signal'
is optional.
import { Controller } from 'cerebral'
import Router from '@cerebral/router'
const controller = Controller({
modules: {
router: Router({
routes: [
{
path: '/projects/:projectId',
map: { projectId: state`app.currentProjectId` },
signal: 'app.projectRouted'
},
{
path: '/settings/:tab',
map: { tab: props`tab`, focus: props`focus` },
signal: 'app.settingsRouted'
}
]
})
}
})
computed mapping
You can use a Compute value here to run a computed in order to prepare
the value passed to build the url.
map: {
urlKey: Compute()
}
If you use a Compute the router cannot map back from the url key to the
state and you need to define a reverse map with rmap:
rmap: {
'some.state': Compute(props`urlKey`, (urlKey) => ),
'other.state': Compute(props`urlKey`, (urlKey) => )
}
import { Controller } from 'cerebral'
import Router from '@cerebral/router'
import { props, state } from 'cerebral/tags'
const controller = Controller({
modules: {
router: Router({
routes: [
{
path: '/settings/:tab',
map: {
opts: Compute(
state`projectId`,
state`user.lang`,
(projectId, lang) => ({ projectId, lang })
)
},
rmap: {
projectId: Compute(
state`projectId`,
props`opts`,
(projectId, opts) => opts.projectId || projectId
),
'user.lang': Compute(
state`validLangs`,
props`opts`,
(validLangs, opts) => (validLangs[opts.lang] ? opts.lang : 'en')
)
}
}
],
query: true
})
}
})
Dynamically add routes
Apps that use code splitting for security reasons may not want to define all routes until after the user has been verified.
The addRoutes() method allows routes to be added after the app has been initialized.
Define your initial set of routes as normal:
import Router from '@cerebral/router'
export default Router({
routes: [
{ path: '/', signal: 'homeRouted' },
{ path: '/login', signal: 'loginRouted' }
]
})
Then later you can call addRoutes:
import router from './router'
router.addRoutes([
{ path: '/now-you-see-me', signal: 'hiddenModule.hiddenRouted' }
])
When used together with code splitting and controller.addModule() you can dynamically add functionality to a running cerebral application.
The only gotcha is that you might need to refresh the current route when reloading the app. Due to the order of events, the router may fire before the routes have loaded.
import { reload } from '@cerebral/router/operators'
import checkAuthToken from '../actions/checkAuthToken'
import addExtraRoutes from '../actions/addExtraRoutes'
export default [
checkAuthToken,
{
valid: [
addExtraRoutes,
reload
],
invalid: []
}
]