express-crud-router

Expose resource CRUD (Create Read Update Delete) routes in your Express app. Compatible with React Admin Simple Rest Data Provider. The lib is ORM agnostic. List of existing ORM connectors.

1import crud from 'express-crud-router'
2
3app.use(
4  crud('/admin/users', {
5    get: ({ filter, limit, offset, order }) =>
6      User.findAndCountAll({ limit, offset, order, where: filter }),
7    create: body => User.create(body),
8    update: (id, body) => User.update(body, { where: { id } }),
9    destroy: id => User.destroy({ where: { id } }),
10  })
11)

Note: Content-Range header

For getList methods, the response includes the total number of items in the collection in X-Total-Count header. You should use this response header for pagination and avoid using Content-Range header if your request does not include a Range header. Checkout this stackoverflow thread for more info.

If you are using ra-data-simple-rest, please refer to the documentation to use X-Total-Count for pagination.

Install

npm install express-crud-router

Usage

Simple use case

1import express from 'express'
2import crud from 'express-crud-router'
3import sequelizeCrud from 'express-crud-router-sequelize-v6-connector'
4import { User } from './models'
5
6const app = new express()
7app.use(crud('/admin/users', sequelizeCrud(User)))

Limit actions

1import express from 'express'
2import crud from 'express-crud-router'
3import sequelizeCrud from 'express-crud-router-sequelize-v6-connector'
4import { User } from './models'
5
6const app = new express()
7app.use(
8  crud('/admin/users', {
9    ...sequelizeCrud(User),
10    destroy: null,
11  })
12)

Custom filters

Custom filters such as case insensitive filter can be perform like this:

1import express from 'express'
2import { Op } from 'sequelize'
3import crud from 'express-crud-router'
4import sequelizeCrud from 'express-crud-router-sequelize-v6-connector'
5import { User } from './models'
6
7const app = new express()
8app.use(
9  crud('/admin/users', sequelizeCrud(User), {
10    filters: {
11      email: value => ({
12        email: {
13          [Op.iLike]: value,
14        },
15      }),
16    },
17  })
18)

Custom filter handlers can be asynchronous. It makes it possible to filter based on properties of a related record. For example if we consider a blog database schema where posts are related to categories, one can filter posts by category name thanks to the following filter:

1crud('/admin/posts', actions, {
2  filters: {
3    categoryName: async value => {
4      const category = await Category.findOne({ name: value }).orFail()
5
6      return {
7        categoryId: category.id,
8      }
9    },
10  },
11})

Notes:

• the filter key (here categoryName) won't be passed to the underlying action handler.
• there is no support of conflicting attributes. In the following code, one filter will override the effect of the other filter. There is no garantee on which filter will be prefered.

1crud('/admin/posts', actions, {
2  filters: {
3    key1: async value => ({
4      conflictingKey: 'hello',
5    }),
6    key2: async value => ({
7      conflictingKey: 'world',
8    }),
9  },
10})

Additional attributes

Additional attributes can be populated in the read views. For example one can add a count of related records like this:

1crud('/admin/categories', actions, {
2  additionalAttributes: {
3    postsCount: category => Post.count({ categoryId: category.id })
4  },
5  additionalAttributesConcurrency: 10 // 10 queries Post.count will be perform at the same time
6})

additionalAttributes function parameters are:

• the current row
• an object: {rows, req} where rows are all page rows and req is the express request.

Similarly to how react-admin deals with resource references, express-crud-router provides additional field helpers:

• populateReference
• populateReferenceMany
• populateReferenceManyCount
• populateReferenceOne

Using additionalAttributes with populateReferenceManyCount or populateReferenceOne can be useful instead of using react-admin ReferenceManyCount and ReferenceOne as they are often used in list views and generate one HTTP query per row.

1crud<number, { id: number }>('/users', {
2  get: jest.fn().mockResolvedValue({
3    rows: [{ id: 1 }, { id: 2 } , { id: 3 }],
4    count: 2
5  }),
6}, {
7  additionalAttributes: {
8    posts: populateReferenceMany({
9      fetchAll: async () => [
10        {id: 10, authorId: 1},
11        {id: 11, authorId: 1},
12        {id: 12, authorId: 2},
13      ],
14      target: 'authorId'
15    })
16  }
17})

Custom behavior & other ORMs

1import express from 'express'
2import crud from 'express-crud-router'
3import { User } from './models'
4
5const app = new express()
6app.use(
7  crud('/admin/users', {
8    get: ({ filter, limit, offset, order }, { req, res }) =>
9      User.findAndCountAll({ limit, offset, order, where: filter }),
10    create: (body, { req, res }) => User.create(body),
11    update: (id, body, { req, res }) => User.update(body, { where: { id } }),
12    destroy: (id, { req, res }) => User.destroy({ where: { id } }),
13  })
14)

An ORM connector is a lib exposing an object of following shape:

1interface Actions<R> {
2  get: GetList<R> = (conf: {
3    filter: Record<string, any>
4    limit: number
5    offset: number
6    order: Array<[string, string]>
7  }) => Promise<{ rows: R[]; count: number }>
8  create: (body: R) => Promise<R & { id: number | string }>
9  destroy: (id: string) => Promise<any>
10  update: (id: string, data: R) => Promise<any>
11}

Search

Autocomplete

When using react-admin autocomplete reference field, a request is done to the API with a q filter. Thus, when using the autocomplete field in react-admin, you must specify the behavior to search the records. This could looks like:

1app.use(
2  crud('/admin/users', , sequelizeCrud(User), {
3    filters: {
4      q: q => ({
5          [Op.or]: [
6            { address: { [Op.iLike]: `${q}%` } },
7            { zipCode: { [Op.iLike]: `${q}%` } },
8            { city: { [Op.iLike]: `${q}%` } },
9          ],
10        }),
11    },
12  })
13)

express-crud-router ORM connectors might expose some search behaviors.

Recipies

Generic filter on related record attributes

1crud('/admin/posts', actions, {
2  filters: {
3    category: async categoryFilters => {
4      const categories = await Category.find(categoryFilters)
5
6      return {
7        categoryId: categories.map(category => category.id),
8      }
9    },
10  },
11})

This code allows to perform queries such as:

/admin/posts?filter={"category": {"name": "recipies"}}

Contribute

This lib uses semantic-release. You need to write your commits following this nomenclature:

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, - formatting, missing semi-colons, etc)
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing or correcting existing tests
• chore: Changes to the build process or auxiliary tools and libraries such as documentation generation

To trigger a major version release write in the core of the commit message:

feat: my commit

BREAKING CHANGE: detail here

Thanks

Thank you to Lalilo who made this library live.