Does the line

# import Post from "./generated/prisma.graphql"

in schema.graphql do anything? If I remove it i get errors. I'm using the standard node-advance boilerplate from graphql create

yes, it imports the

Post

type from

./generated/prisma.graphql

🙂

I found it a little confusing becuse I didn't need to add anything when adding new types to the datamodel

It's an import that allows your schema to use the type Post. The generated prisma.graphql is very important. Without that import it wouldn't know what "Post" meant. Look in that generated file for "type Post". If you define new types in your own schema then that's all where it's defined.

@ameistad are the other types related to

Post

by any chance? 🙂 importing is transitive, so that might explain it

It's also an interesting idea to consider when you might want to define your own slightly different Post type in your schema. For example, the User type has the password field. In my server I personally defined a new type User without that password field and removed my import for User from the generated file.

that's indeed a common pattern, thanks for sharing @KyleG!

@nilan: Yes, I had a one to many relation. So that might be it.

Just feel like sharing, I hope this could give you an idea. But here, in my little practice project (a movie collection database thingie) I this is generated: and this is my (two) different kinds of users (I hide email as well, since I may not want email to be publicly shared when someone, for example, queries a movie's createdBy field (type User))