I have a resolver to create a new draft. I have a ...
# orm-helpd
doums
10/10/2018, 4:49 PMI have a resolver to create a new draft. I have a relation between User and Draft. So my resolver looks like this :
Copy code
async createDraft(parent, { text }, ctx) {
const userId = getUserId(ctx)
console.log(userId) //userId is OK
return ctx.prisma.createDraft({
text,
author: {
connect: { id: userId }
}
})
}n
nikolasburk
10/10/2018, 4:54 PM
what does your Prisma datamodel look like?
d
doums
10/10/2018, 4:54 PM Copy code
type Draft {
id: ID! @unique
createdAt: DateTime!
updatedAt: DateTime!
text: String!
author: User
}
type User {
id: ID! @unique
email: String! @unique
password: String!
username: String! @unique
posts: [Draft!]!
}n
nikolasburk
10/10/2018, 4:55 PM
Is there an error message?
d
doums
10/10/2018, 4:55 PMnope
doums
10/10/2018, 4:56 PMIn my schema I redefine the user type like this
doums
10/10/2018, 4:56 PM Copy code
type User {
id: ID!
email: String!
username: String!
drafts: [Draft!]!
}n
nikolasburk
10/10/2018, 4:56 PM
hmm that shouldn't be problem
nikolasburk
10/10/2018, 4:57 PM
I assume you verified that the
createDraftd
doums
10/10/2018, 4:58 PMyep
doums
10/10/2018, 4:58 PMActually I testing the mutation directly in the playground
doums
10/10/2018, 4:58 PMso I can see the server response
doums
10/10/2018, 4:59 PM Copy code
{
"data": {
"createDraft": {
"id": "cjn3ee0ql007f0a94xesulgbb",
"createdAt": "2018-10-10T16:57:58.844Z",
"updatedAt": "2018-10-10T16:57:58.844Z",
"text": "145",
"author": null
}
}
}n
nikolasburk
10/10/2018, 5:00 PM
ah ok, I'm guessing that the data was actually create properly, it's just the server response that's wrong!
nikolasburk
10/10/2018, 5:01 PM
did you implement a resolver for the
authorDraftnikolasburk
10/10/2018, 5:01 PM
d
doums
10/10/2018, 5:03 PMnope
n
nikolasburk
10/10/2018, 5:03 PM
this should fix it:
Copy code
const resolvers = {
Query: {
// ...
},
Mutation: {
// ...
},
Draft: {
author(parent, args, ctx) {
return ctx.prisma.draft({id: parent.id}).author()
}
},
User: {
posts(parent, args, ctx) {
return ctx.prisma.user({id: parent.id}).posts()
}
}
}d
doums
10/10/2018, 5:04 PMOk I understand now
💯 1
doums
10/10/2018, 5:05 PMthank you
doums
10/10/2018, 5:07 PMBefore, using prisma binding there is no need to implement a resolver for author field
3 Views