We have many years of experience building and reviewing enterprise applications using Angular. Most applications communicate with apis and use state management patterns for their UIs, preferably with @ngrx, @ngxs or Akita.
We were able to reduce a lot of boilerplate code with @ngrx/data, but the way data was fetched and displayed was still hard to figure out in most applications. We needed to look through reducers, effects, resolvers and components in order to understand how data is flowing.
Ideally, we figured, you should be able to read an application's data flow simply by looking at its routes. So we came up with a data flow pattern solution that hooks into Angular's router (and a silly name). Here is @ng-frrri/router-middleware.
import { operate } from '@ng-frrri/router-middleware';
import { getMany, getActive, reset } from '@ng-frrri/router-middleware/operators';
const all = 'entities';
const posts = 'entities.posts';
const routes: Routes = [
{
path: 'posts',
data: operate(
reset(all),
getMany(posts),
),
children: [
{
path: ':id',
data: operate(
getActive(posts),
),
},
],
},
];As of now, we have integrated our router-middleware with @ngxs, our state management solution of choice these days. Until documentation catches up, see the ng-integration example in the GitHub repository.
