Skip to main content

Limitations & Known Issues

  • No JSON column support.
    • nestjs-prisma-crud assumes a nested object is a relation.
    • Suggested workaround if you really want JSON objects: use middleware for transforming into string on both frontend and backend
    • Planned for v1.x.x
  • Prisma keywords may not be used as model properties
    • TODO: document or link which are those
  • No type safety: given the crudQuery's dynamic nature, PrismaCrudService makes no effort to provide type safety on it's return values.
    • If you really need great type safety, its recommended that you create a plain NestJS + Prisma controller.
  • No bulk operations
    • And no planned support at this point.

Roadmap for v1#

  • Backend nested create
  • Backend nested update
  • Simple GET read one/many
  • Delete
  • Complex GET Frontend QueryBuilding
    • Allow specifying joins from frontend (as long as allowed on backend)
    • Allow clients to specify select fields (only, except).
    • Pagination
      • Configurable pagination defaults (pageSize min/max)
      • OrderBy validation
    • Allow complex where
  • Access control policy strategy
    • Default utility guards
    • Rename crudQ
    • Examples
  • crud schematics
  • improve module configuration
  • additional transaction support tests and implementation.
  • test nested create cannot happen passed allowed joins
  • rename AccessPolicyModule to AccessControlModule
  • Test access control plays nicely with websockets

Roadmap for v1.x.x#

  • Configurable global settings
  • Some JSON support
  • Start benchmarking

Thank You#

We hope you will enjoy nestjs-prisma-crud!