Hello all. Having an issue, hopefully someone here...
# orm-helpj
jdoyle112
12/20/2018, 3:18 PMHello all. Having an issue, hopefully someone here can help. I have a prisma server with a mutation where I’m trying to pass an ID to make a connection. Here is what it looks like..
createNotification(title: String!, message: String!, seen: Boolean, type: NotificationType, userId: ID!): Notification!
But I get an error saying “userId is not defined. Did you mean user?”
p
Priyank Patel
12/20/2018, 3:47 PMCan you paste your mutation schema?
j
jdoyle112
12/20/2018, 4:01 PMasync createNotification(parent, args, ctx, info) {
const { userId } = ctx.request;
if (!userId) {
throw new Error(‘You must be logged in’);
}
const notification = await ctx.db.mutation.createNotification({
data: {
user: { connect: { id: args.userId } },
...args
}
}, info);
return notification;
},
jdoyle112
12/20/2018, 4:02 PM@Priyank Patel
p
Priyank Patel
12/20/2018, 4:11 PMin your schema.graphql, do you have userId defined for createNotification mutation?
j
jdoyle112
12/20/2018, 4:12 PMThis is what the mutation looks like in my schema.graphql
jdoyle112
12/20/2018, 4:12 PMcreateNotification(title: String!, message: String!, seen: Boolean, type: NotificationType, userId: ID!): Notification!
jdoyle112
12/20/2018, 4:12 PMuserId is there
p
Priyank Patel
12/20/2018, 4:20 PMoh I know what the problem is, ...args also passes in userId
j
jdoyle112
12/20/2018, 4:23 PMI changed it to “personId” and still no luck
p
Priyank Patel
12/20/2018, 4:23 PMyou should manually specify the field, OR structure the object and then pass it on
Priyank Patel
12/20/2018, 4:25 PMasync createNotification(parent, args, ctx, info) {
const { userId } = ctx.request;
const { title, message, seen, type } = args;
if (!userId) {
throw new Error(‘You must be logged in’);
}
const notification = await ctx.db.mutation.createNotification({
data: {
user: { connect: { id: args.userId } },
title,
* message,*
* seen,*
* type*
}
}, info);
return notification;
},
Priyank Patel
12/20/2018, 4:25 PMTry this out
j
jdoyle112
12/20/2018, 4:27 PMThat works but I there are situations where I need to create a notification for a user that is not the one making the request. Although that would work
jdoyle112
12/20/2018, 4:28 PMSo I’m able to do this..
createNotification(title: String!, message: String!, belongsTo: UserCreateOneInput!): Notification!
And then the mutation looks like this..
mutation {
createNotification(
title: “Test”,
message: “This is a test notification”,
belongsTo: {
connect: {
id: “******”
}
}
){
id
}
}
But that’s annoying to pass that object to the request every time. I’d rather just pass the id
p
Priyank Patel
12/20/2018, 4:38 PMmutation {
createNotification(
title: “Test”,
message: “This is a test notification”,
userId: "USER_ID"
){
id
}
}
Priyank Patel
12/20/2018, 4:38 PMIt should be something like this. I don't ever remember passing belongTo in the mutation request
j
jdoyle112
12/20/2018, 4:44 PMSorry I changed user in my datamodel to belongsTo.
jdoyle112
12/20/2018, 4:44 PMAre you saying pass it as a string instead of an ID?
p
Priyank Patel
12/20/2018, 4:45 PMthe id should be form of a string, within double quotation
j
jdoyle112
12/20/2018, 4:46 PMOk I’ll try that, thanks for the help
jdoyle112
12/20/2018, 4:47 PMI do have another mutation that follows this same approach though where I pass ID and not a string. Odd that it works for that and not this. Feels like a bug with the generated prisma file.