Question about generated update input types from SDLInputs()

[paljs]

Question about generated update input types from SDLInputs()

[pakatagoh]

Thanks for info!

and yes if there could be some kind of flag in the paljs config that we could use together with generator:'sdl' so that sdlInputs() will not choose the types that require setand it'll be more "prisma1-friendly"

I guess it could look something like the following?

// pal.js config
module.exports = {
  backend: {
    generator: 'sdl',
    output: 'gql/src/typedefs',
    doNotuseFieldUpdateOperationsInput: true // defaults to false.  This is just a suggestion. I'm not sure what would be a good name or a good place to indicate this flag
};

Will probably have to indicate in the documentation that this will not generate graphql type defs that support prisma2.6 and above.

[AhmedElywa]

Why we use Object not string type?
Because the Number fields have many options like:

from prisma release notes https://github.com/prisma/prisma/releases/tag/2.6.0

We are introducing five atomic operations for Int and Float fields :

increment: x: Adds x to the current value
decrement: x: Subtracts x from the current value
multiply: x: Multiplies the current value by x
divide: x: Divides the current value by x
set: x: Sets the value to x (equivalent to data: { age: 18 })

And Also for Json fields must with set

In the end, I can add an option for you to pass into SDLInputs() function

[AhmedElywa]

Can you tell me if you using my generator with Javascript or Typescript?

[pakatagoh]

Can you tell me if you using my generator with Javascript or Typescript?

we are using typescript 👍🏻