clayrisser / nestjs-crud-prisma Goto Github PK

View Code? Open in Web Editor NEW

59.0 2.0 13.0 1.06 MB

crud for restful apis built with nestjs and prisma

License: MIT License

Makefile 31.44% TypeScript 66.28% Dockerfile 1.39% Shell 0.89%

nestjs-crud-prisma's People

Stargazers

Watchers

Forkers

sebacruz sedoyjan terryjoo doender apperside bleafman wooodhead linecode michalkow ms10596 vutadev

nestjs-crud-prisma's Issues

Library does not follow prisma naming schema anymore

As per their docs, the new naming convention for table names use PascalCase. This library, on the other hand, uses camelCase as per:

nestjs-crud-prisma/src/prismaCrudService.ts

Lines 55 to 56 in 77514a4

 this.tableName = camelcase(entity.name); 

 this.client = this.prisma[this.tableName];

This causes the whole library to break. Would it be possible to either use PascalCase instead or, at the very least, make the table name configurable? (maybe have a passed in options parameter or something?)

Add support for upsert?

Prisma supports upserting. I'm not sure which REST endpoint would be responsible for upserting but it could be super useful.

Add support for joins

Ignore invalid queries with warning

https://github.com/silicon-hills/nestjs-crud-prisma/blob/master/src/prismaCrud.service.ts#L268

`client.findOne` is not a function

I'm getting this error requesting a single entity, /users/1 for example.

[Nest] 47207   - 06/20/2021, 6:27:47 AM   [ExceptionsHandler] _this6.client.findOne is not a function +17556ms
TypeError: _this6.client.findOne is not a function
    at /Users/sebas/Sites/ponty.app/node_modules/nestjs-crud-prisma/src/prismaCrudService.ts:389:24
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/Users/sebas/Sites/ponty.app/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
    at _next (/Users/sebas/Sites/ponty.app/node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)
    at /Users/sebas/Sites/ponty.app/node_modules/@babel/runtime/helpers/asyncToGenerator.js:32:7
    at new Promise (<anonymous>)
    at /Users/sebas/Sites/ponty.app/node_modules/@babel/runtime/helpers/asyncToGenerator.js:21:12
    at UsersService.getOne (/Users/sebas/Sites/ponty.app/node_modules/nestjs-crud-prisma/src/prismaCrudService.ts:387:46)
    at UsersController.getOneBase (/Users/sebas/Sites/ponty.app/node_modules/@nestjsx/crud/src/crud/crud-routes.factory.ts:211:27)
    at /Users/sebas/Sites/ponty.app/node_modules/@nestjs/core/router/router-execution-context.js:38:29

On the master branch the PrismaCrudService is using the findUnique method but in the npm package it's using findOne.

Handle or/and hashmap query

The following type of query needs to be supported.

?s={"name": {"$or": {"$isnull": true, "$eq": "Superman"}}}

https://github.com/nestjsx/crud/wiki/Requests#search

clayrisser / nestjs-crud-prisma Goto Github PK

nestjs-crud-prisma's People

Stargazers

Watchers

Forkers

nestjs-crud-prisma's Issues

Library does not follow prisma naming schema anymore

Add support for upsert?

Add support for joins

Ignore invalid queries with warning

`client.findOne` is not a function

Handle or/and hashmap query

Any update for this ?

Enforce only filter/or/search

Validate pagination works correctly for searches

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

Jobs

	this.tableName = camelcase(entity.name);
	this.client = this.prisma[this.tableName];