Hey folks - having an issue where I can’t add a ne...
# prisma-whats-new
w
Hey folks - having an issue where I can’t add a new field in my
datamodel.graphql
- recorded a quick vid on it: http://wes.io/pP18 cc @nilan
It might be because that user already exists? Can I not add a new optional field after a type has been created?
n
thanks for sharing that video, super helpful. when you go to your Prisma endpoint using the Playground manually, can you actually query the
cool
field?
w
@nilan the local one? Or direct to that endpoint?
n
directly to that endpoint
w
let me turn off the auth and try
@nilan just get null https://graphqlbin.com/v29Ai7
n
cool, that's all expected
w
@nilan if I create another user and query it, it works fine
so the problem must be with yoga?
n
so then it looks like an issue in
prisma-binding
, or in the way you laid out
schema.graphql
. I don't fully understand it yet, but I will try to dig into it. I'll create an issue on Github 🙂
w
@nilan I tried adding the field to schema.graphql too
note the field here is “resetToken” now
n
@wesbos I had the same use case as yours and it is working for me. I am using prisma version prisma/1.1.2. I added a new field in a type and queried it and it does give me result instead of an error.
n
this turned out to be a problem with the endpoint entered in
.env
🙂 difficult to find! thinking about improving the docs around this topc
thanks for your help @Nikhil 🙏