CCBCodeMonkey
11/13/2018, 7:30 AMCCBCodeMonkey
11/13/2018, 7:30 AMNick
11/13/2018, 10:24 AMyantakus
11/13/2018, 11:31 AMvotePost
resolver?
My current datamodel is the following:
type Video {
...
votes: [Vote!]! @relation(name: "VideoVotes")
voteScore: Int! @default(value: 0)
}
type Vote {
id: ID! @unique
parent: Video! @relation(name: "VideoVotes")
user: User! @relation(name: "UserVotes")
type: VoteType!
}
type User {
...
votes: [Vote!]! @relation(name: "UserVotes")
}
enum VoteType {
UP
DOWN
}
fgreinus
11/13/2018, 11:43 AMfgreinus
11/13/2018, 11:43 AMsiyfion
11/13/2018, 2:16 PMprisma generate
and it not doing _anything_… no generated files, no errors, nothing.yolen
11/13/2018, 2:26 PMprolink007
11/13/2018, 3:25 PMupdatedAt
field is not working. I am seeing the same issue as reported in this bug in a later version. Is this bug still an issue?
https://github.com/prisma/prisma/issues/2539Alex
11/13/2018, 4:54 PMCCBCodeMonkey
11/13/2018, 5:01 PMNaka
11/13/2018, 5:08 PMwontwon
11/13/2018, 5:49 PMDrew Delianides
11/13/2018, 6:11 PM[at-loader] ./src/utils.ts:81:19
TS2345: Argument of type '"{ role }"' is not assignable to parameter of type '{ [key: string]: any; } | undefined'.
It seems the typescript doesn't like when I pass a string into a query/mutation instead of the info
object.mario
11/13/2018, 6:57 PMNaka
11/13/2018, 6:58 PMError R14 (Memory quota exceeded)
Process running mem=568M(111.1%)
mario
11/13/2018, 6:58 PMNaka
11/13/2018, 7:00 PMmario
11/13/2018, 7:01 PMNaka
11/13/2018, 7:02 PMCCBCodeMonkey
11/13/2018, 7:14 PMCCBCodeMonkey
11/13/2018, 7:15 PMtoo many characters in field x
field: x
roberto.guerra
11/13/2018, 7:47 PMroberto.guerra
11/13/2018, 7:47 PMIDL style imports
. But the concept/idea is sane…. so was wondering if anyone used something like this for Prisma.jdoyle112
11/13/2018, 8:11 PMjdoyle112
11/13/2018, 8:12 PMNaka
11/13/2018, 8:19 PMid_contains
in your where variables and it is breaking the query.Nena
11/13/2018, 8:35 PMschema.graphql
and it has all Types in there, and I know that Prisma automatically creates queries, mutations and subscriptions for me, but I want to define my own subscription. Tried doing is inside of schema.graphql
like type Subscription...
but when I run it in here https://us1.prisma.sh/nevena-djaja/explorer-graphql/dev I get "The provided query doesn't include any known model name. Please check for the latest subscriptions API."
Any ideas how to solve this?Tamir
11/13/2018, 8:36 PMRamin B
11/13/2018, 9:01 PMtype MemberForm {
id: ID! @unique
name: String! @unique
description: String
formEntries: [MemberFormEntry!]!
}
type MemberFormEntry {
id: ID! @unique
form: [MemberForm!]!
formItem: MemberFormItem!
required: Boolean @default(value: "false")
weight: Int
label: String
placeholder: String
hint: String
}
type MemberFormItem {
id: ID! @unique
name: String! @unique
kind: FormItemKind @default(value: "TEXT")
formEntry: MemberFormEntry
}
relevant api schema:
# import {} from './generated/prisma.graphql'
type Query {
memberForms: [MemberForm!]!
}
relevant resolver:
memberForms: (parent, args, ctx, info) => ctx.db.query.memberForms(info)
However, when I run the following query, I don’t get any formEntries
back:
memberForms {
id
formEntries {
id
}
}