> For the complete documentation index, see [llms.txt](https://bitflut.gitbook.io/ng-frrri/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bitflut.gitbook.io/ng-frrri/master.md).

# Introduction

## 🏎️ 🏎️ @ng-frrri/router-middleware 🏎️ 🏎️

> Data flow at 250 MPH

### Synopsis

We have many years of experience building and reviewing enterprise applications using Angular. Most applications communicate with CRUD APIs and use state management patterns for their UIs, preferably with [@ngrx](https://ngrx.io/), [@ngxs](https://www.ngxs.io/) or [Akita](https://netbasal.gitbook.io/akita/).

We were able to reduce a lot of boilerplate code with [@ngrx/data](https://ngrx.io/guide/data), but the way data was fetched and displayed was still hard to figure out reading these applications. We needed to look through reducers, effects, resolvers and components in order to understand how data is flowing to the UI.

Ideally, we figured, you should be able to define an application's data flow simply by looking at the routes. So we came up with a data flow pattern that hooks into Angular's router (and a silly name). Here is **@ng-frrri/router-middleware**.

### What it looks like:

```typescript
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 = frrri(
    [
        {
            path: 'posts',
            data: operate(
                reset(all),
                getMany(posts),
            ),
            children: [
                {
                    path: ':id',
                    data: operate(
                        getActive(posts),
                    ),
                },
            ],
        },
    ]
);

```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bitflut.gitbook.io/ng-frrri/master.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.