Prisma

Screen Shot 2019-03-08 at 4.03.48 PM.png

Hello all, can someone help me with this error in VS code ? I thought the createdAt &amp; updatedAt are automatically filled

It says in the error. `Type 'number' is not assignable to type 'DateTimeInput'`. `Date.now()` returns a number.

It's also maintained by Prisma. You need not fill it. (AFAIK)

Thank you <@UBGNKDHK9>,Yeah that was my question, I do understand the error :slightly_smiling_face: if someone can shade the light on why it's giving me the error while Prisma is maintaining the createdAt &amp; updatedAt fields, that would be great

Screen Shot 2019-03-08 at 4.25.28 PM.png

attaching another screenshot with the root cause

<@UBGNKDHK9> it's saying it's missing up here :point_up_2:

I can see that. Why happens if you pass `new Date(Date.now())`? 

Also, that does the type `DateTimeInput` look like in your schema?

That is autogenerated ```/*
DateTime scalar input type, allowing Date
*/
export type DateTimeInput = Date | string;```

it works if I did this ```    return ctx.prisma.createPost({
      title,
      content,
      author: {
        connect: { id: userId },
      },
      createdAt: new Date(Date.now()),
      updatedAt: null
    })``` but I shouldn't be the one caring about setting those fields, that's my problem

Shouldn’t Prisma be setting these timestamps for us?

In your SDL, is `createdAt` set to `DateTime!`? If it is - remove the `!`. Should make the input nullable.

ok will test it, but making it nullable might leave it null forever Thanks again <@UBGNKDHK9>  I will check and get back if the problem still presists

Hey man, no worries! Holla if you need me!

Screen Shot 2019-03-08 at 6.27.44 PM.png

unfortunately it's setting the fields with null now after I created the post, I am wondering if there something wrong with my config, btw I forgot to mention that I am using GraphQL nexus

I believe it's a bit different from the prisma code I saw in the tutorial app

I've been using graphql nexus as well. Very odd that it's set to null. I'll try and see if I can solve it myself. Will update you if I can.

I found the issue, I wasn't using the correct directives <https://www.prisma.io/docs/1.27/datamodel-and-migrations/datamodel-MONGO-knun/#example>