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    getList: ({ filter, limit, offset, order }) =>
6      User.findAndCountAll({ limit, offset, order, where: filter }),
7    getOne: id => User.findByPk(id),
8    create: body => User.create(body),
9    update: (id, body) => User.update(body, { where: { id } }),
10    destroy: id => User.destroy({ where: { id } }),
11  })
12)

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        [Op.iLike]: value,
13      }),
14    },
15  })
16)

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    getList: ({ filter, limit, offset, order, opts: { req, res } }) =>
9      User.findAndCountAll({ limit, offset, order, where: filter }),
10    getOne: (id, { req, res }) => User.findByPk(id),
11    create: (body, { req, res }) => User.create(body),
12    update: (id, body, { req, res }) => User.update(body, { where: { id } }),
13    destroy: (id, { req, res }) => User.destroy({ where: { id } }),
14  })
15)

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

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

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', {
3    search: async (q, limit) => {
4      const { rows, count } = await User.findAndCountAll({
5        limit,
6        where: {
7          [Op.or]: [
8            { address: { [Op.iLike]: `${q}%` } },
9            { zipCode: { [Op.iLike]: `${q}%` } },
10            { city: { [Op.iLike]: `${q}%` } },
11          ],
12        },
13      })
14
15      return { rows, count }
16    },
17  })
18)

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

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