hey guys, I'm trying since hours to get the contex...
# orm-helpm
markus_str
12/10/2018, 3:30 PMhey guys, I'm trying since hours to get the context.prisma.user({id}) from the examples working in another project. Is this the right channel to ask for help?
p
Priyank Patel
12/10/2018, 4:29 PMWhat is the issue?
m
markus_str
12/10/2018, 4:32 PMHey, I was able to resolve it. Thank you
markus_str
12/10/2018, 4:34 PMI have another question tho:
Copy code
type User {
id: ID! @unique
fibauid: String! @unique
name: String! @unique
email: String! @unique
reviews: [Review!]
}
type Review {
id: ID! @unique
url: String! #check for URL type in frontend?
author: User!
} Copy code
return context.prisma.createReview({
url,
title,
author: {
connect: {
id: userId
},
}
}); Copy code
"Field \"author\" of type \"User!\" must have a selection of subfields. Did you mean \"author { ... }\"?"markus_str
12/10/2018, 4:35 PMi couldn't figure out the syntax to make it work. Also is this 'connect' keyword going to push the Review to the user ?
markus_str
12/10/2018, 4:35 PMreview has a title etc...I just didn't paste everything to stay simple
p
Priyank Patel
12/10/2018, 5:27 PMWhat does your request query look like?
As for the connect question, yes. User will have list of review ids and the author field will have the user id it's associated to.
Priyank Patel
12/10/2018, 5:35 PMIf you are trying to query the list of reviews, try:
Copy code
query {
reviews {
id
url
author {
id
name
}
}
}m
markus_str
12/10/2018, 6:47 PMahh ok, good to know how connect works
markus_str
12/10/2018, 6:47 PM Copy code
context.prisma.createReview({
url,
title,
author: {
connect: {
id: userId
},
}
});markus_str
12/10/2018, 6:47 PMthis is the mutation
markus_str
12/10/2018, 6:48 PMgiven my shema from above it should work, but it doesn't
markus_str
12/10/2018, 6:51 PMdunno where to put the subfields there
p
Priyank Patel
12/10/2018, 6:51 PMCan you post your mutation request?
m
markus_str
12/10/2018, 6:52 PM Copy code
createReview: async (parent, { url, title }, context, info) => {
const userId = await getUserId(context, info);
return context.prisma.createReview({
url,
title,
author: {
connect: {
id: userId
}
}
});
},p
Priyank Patel
12/10/2018, 6:52 PMAh, there is your problem.
m
markus_str
12/10/2018, 6:52 PMaja
p
Priyank Patel
12/10/2018, 6:53 PMwait, nevermind. This is the resolver.
Priyank Patel
12/10/2018, 6:54 PMCan you try this?
m
markus_str
12/10/2018, 6:54 PMit's weird because if I remove the relation to reviews in my data schema it works
markus_str
12/10/2018, 6:54 PMlike if User doesn't have a review field
markus_str
12/10/2018, 6:54 PMbut just Review has an author field...but then it's kinda pointless
p
Priyank Patel
12/10/2018, 6:55 PM Copy code
mutation {
createReview(
url: "<http://google.com>"
title: "Test Title"
) {
id
url
author {
id
name
}
}
}Priyank Patel
12/10/2018, 6:56 PMAre you executing the mutation like the request above?
m
markus_str
12/10/2018, 6:57 PM Copy code
const CREATE_REVIEW_MUTATION = gql`
mutation createReview($title: String!, $url: String!) {
createReview(title: $title, url: $url) {
id
title
url
createdAt
author
}
}
`;markus_str
12/10/2018, 6:57 PMthis is my apollo mutation
markus_str
12/10/2018, 6:57 PMI then execute it through the UI
markus_str
12/10/2018, 6:57 PMwhat you posted doesn't do the connect right?
p
Priyank Patel
12/10/2018, 6:57 PM Copy code
const CREATE_REVIEW_MUTATION = gql`
mutation createReview($title: String!, $url: String!) {
createReview(title: $title, url: $url) {
id
title
url
createdAt
author {
id
}
}
}
`;Priyank Patel
12/10/2018, 6:57 PMtry that, and note the author field
Priyank Patel
12/10/2018, 6:58 PMyou cannot just call author, you need to specify the fields within the author
Priyank Patel
12/10/2018, 6:58 PMYour resolver is correct, it's the apollo mutation that needed change to the author
m
markus_str
12/10/2018, 6:59 PMmhh ahh ok let me try
markus_str
12/10/2018, 7:07 PMYou are creating a required field but there are already nodes present that would violate that constraint.
markus_str
12/10/2018, 7:08 PMwanted to add reviews field to User.
markus_str
12/10/2018, 7:08 PMI guess that means I have to delete manually all the review or user nodes idk
p
Priyank Patel
12/10/2018, 7:12 PMtry changing the reviews: [Review!] to reviews: [Review!]!. As far I know, everything else seems to be correct.
m
markus_str
12/10/2018, 7:17 PMI deleted all the reviews and it still says there's nodes that violate that....
markus_str
12/10/2018, 7:17 PMreviews:[Review!]! won't work, because a new User doesn't yet have reviews
p
Priyank Patel
12/10/2018, 7:18 PMDid you also also clear all the review id's from user?
m
markus_str
12/10/2018, 7:18 PMusers didn't yet have reviews
markus_str
12/10/2018, 7:18 PMso I deleted all the users as well
markus_str
12/10/2018, 7:18 PM;_)
markus_str
12/10/2018, 7:18 PMlet's see
p
Priyank Patel
12/10/2018, 7:21 PMI'm creating an example repo for you once I test it myself.
m
markus_str
12/10/2018, 7:22 PM"Variable '$data' expected value of type 'UserCreateInput!'
markus_str
12/10/2018, 7:22 PMwhy does this show up again...
markus_str
12/10/2018, 7:22 PMI have a normal createUser function
markus_str
12/10/2018, 7:22 PM Copy code
createUser(name: String!, fibauid: String!, email: String!): Usermarkus_str
12/10/2018, 7:23 PMnow it's buggy again. I don't get why it's always asking for UserCreateInput
markus_str
12/10/2018, 7:25 PMI put in a total of 25hours with prisma and graphql and I can't even get it working idk ... :=(
markus_str
12/10/2018, 7:26 PMp
Priyank Patel
12/10/2018, 7:29 PMYour server is hosted locally, so I won't be able to access it via graphqlbin.
m
markus_str
12/10/2018, 7:30 PMyeah thought so
markus_str
12/10/2018, 7:30 PMidk why on localhost I can't do a simple resolver
markus_str
12/10/2018, 7:40 PMfound one issue
markus_str
12/10/2018, 7:40 PMthanks for helping me so far
markus_str
12/10/2018, 7:40 PMsomehow learning mongo + node was easier ;(
markus_str
12/10/2018, 7:49 PMstrangle it says
Copy code
Cannot return null for non-nullable field Review.author.p
Priyank Patel
12/10/2018, 7:54 PMhttps://github.com/PR1YANKPAT3L/prisma-demo here you go, sorry took me some time as I am at work.
Priyank Patel
12/10/2018, 7:55 PMYou will have to change the ids to appropriate one.
Priyank Patel
12/10/2018, 7:56 PMPriyank Patel
12/10/2018, 7:56 PMm
markus_str
12/10/2018, 7:59 PMthanks for setting these u
markus_str
12/10/2018, 7:59 PMp
markus_str
12/10/2018, 7:59 PMwait
markus_str
12/10/2018, 7:59 PM Copy code
Review: {
author: ({ id }, args, context) => {
return context.prisma.review({ id }).author()
},
},
User: {
reviews: ({ id }, args, context) => {
return context.prisma.user({ id }).reviews()
},
},markus_str
12/10/2018, 7:59 PMwhat is this? I didn't have those inside the resolvers...
markus_str
12/10/2018, 8:00 PMdidn't show up in the tutorials or?
markus_str
12/10/2018, 8:02 PMI added this two resolvers and it works
markus_str
12/10/2018, 8:02 PMdamn
markus_str
12/10/2018, 8:02 PMwhat the hell. My whole day I'm looking somewhere else and I didn't get this concept
😂 1
markus_str
12/10/2018, 8:03 PMdatamodel => schema => resolver types ...I mean it's a bit convoluted don't you think ?:)
markus_str
12/10/2018, 8:03 PManyways thank you soo much Priyank
markus_str
12/10/2018, 8:03 PMgonna collapse into my bed now
p
Priyank Patel
12/10/2018, 8:10 PMNo worries 😀, feel free to message me if you have any issues.
Priyank Patel
12/10/2018, 8:18 PMThere is a reason why the datamodel and schema are seperated, With datamodel, it creates a basic CRUD service. With schema, it allows you to build on top of the CRUD service with custom query and mutations (creating auth for example).
m
markus_str
12/11/2018, 8:56 AMok that makes a bit more sense now
10 Views