It appears datamodel.prisma and schema.graphql ove...
# orm-helpb
bresson
05/22/2019, 9:57 PMIt appears datamodel.prisma and schema.graphql overlap quite a bit but they have different purposes. Every software dev's DRY radar is of course on fire about keeping two representations of the same data ( even if used for different purposes ) in sync. I thought I found a feature to import schemas into datamodel based on the statement from a similar question ( link below ). Can anyone confirm that this statement will work and help me locate it in the docs? I can't locate it ....
# import User, Note from './datamodel.generated.graphql'
https://www.prisma.io/forum/t/graphcool-1-0-datamodel-graphql-vs-schema-graphql/2063/2
j
Jonathan
05/22/2019, 10:14 PMJonathan
05/22/2019, 10:16 PMthat’s the doc link for graphql-import
Jonathan
05/22/2019, 10:16 PMbut your “import schemas into datamodel” comment sounds backwards to me
Jonathan
05/22/2019, 10:18 PMyou’ll see types in a schema file that closely mirror types in a datamodel, but there’s one or two fields left out in the schema file
👍 1
Jonathan
05/22/2019, 10:18 PMthose are the public-facing bits
Jonathan
05/22/2019, 10:23 PMyou want to store a password with your User model, but you don’t want to allow a client to query for it. so you override the imported, datamodel-defined User type with a definition in your schema file
Jonathan
05/22/2019, 10:26 PM@wesbos covers this pretty well in video 14 of his advanced react course
Jonathan
05/22/2019, 10:44 PM3 Views