Atomic Router
Simple routing implementation that provides abstraction layer instead of inline URL's and does not break your architecture
- Type-safe
- No inline URL's
- Atomic routes
- Does not break architecture
- Framework-agnostic
- Isomorphic (pass your own
history
instance and it works everywhere)
❗️ Attention: At the moment atomic-router team collecting issues and feature requests to redesign and release update. Use current version of atomic-router on your own risk. We are going to write migration guide when/if the release will contain breaking changes. Thank you for reporting issues 🧡
Get view-library bindings
Installation
$ npm install effector atomic-router
Initialization
Create your routes wherever you want:
import { createRoute } from 'atomic-router';
export const homeRoute = createRoute();
import { createRoute } from 'atomic-router';
export const postsRoute = createRoute<{ postId: string }>();
And then create a router
import { createHistoryRouter } from 'atomic-router';
import { createBrowserHistory, createMemoryHistory } from 'history';
import { homeRoute } from '@/pages/home';
import { postsRoute } from '@/pages/posts';
const routes = [
{ path: '/', route: homeRoute },
{ path: '/posts', route: postsRoute },
];
const router = createHistoryRouter({
routes: routes,
});
const history = isSsr ? createMemoryHistory() : createBrowserHistory();
router.setHistory(history);
Why atomic routes?
There are 3 purposes for using atomic routes:
- To abstract the application from hard-coded paths
- To provide you a declarative API for a comfortable work
- To avoid extra responsibility in app features
Examples
Fetch post on page open
- In your model, create effect and store which you'd like to trigger:
export const getPostFx = createEffect<{ postId: string }, Post>(
({ postId }) => {
return api.get(`/posts/${postId}`);
}
);
export const $post = restore(getPostFx.doneData, null);
- And just trigger it when
postPage.$params
change:
import { createRoute } from 'atomic-router';
import { getPostFx } from './model';
const postPage = createRoute<{ postId: string }>();
sample({
source: postPage.$params,
filter: postPage.$isOpened,
target: getPostFx,
});
Avoid breaking architecture
Imagine that we have a good architecture, where our code can be presented as a dependency tree.
So, we don't make neither circular imports, nor they go backwards.
For example, we have Card -> PostCard -> PostsList -> PostsPage
flow, where PostsList
doesn't know about PostsPage
, PostCard
doesn't know about PostsList
etc.
But now we need our PostCard
to open PostsPage
route.
And usually, we add extra responisbility by letting it know what the route is
const PostCard = ({ id }) => {
const post = usePost(id);
return (
<Card>
<Card.Title>{post.title}</Card.Title>
<Card.Description>{post.title}</Card.Description>
{/* NOOOO! */}
<Link to={postsPageRoute} params={{ postId: id }}>
Read More
</Link>
</Card>
);
};
With atomic-router
, you can create a "personal" route for this card:
const readMoreRoute = createRoute<{ postId: id }>();
And then you can just give it the same path as your PostsPage
has:
const routes = [
{ path: '/posts/:postId', route: readMoreRoute },
{ path: '/posts/:postId', route: postsPageRoute },
];
Both will work perfectly fine as they are completely independent
API Reference
const route = createRoute<Params>();
route.$isOpened;
route.$params;
route.$query;
route.opened;
route.updated;
route.closed;
route.open;
route.navigate;