With `prisma-nexus`, how do you expose enums?
# orm-helpl
lawjolla
03/08/2019, 7:14 PMWith
prisma-nexuslawjolla
03/08/2019, 7:17 PMThe hidden
prismaEnumTypew
weakky
03/08/2019, 7:53 PMYou should use prismaEnumType only to customize prisma enums. Otherwise, just use nexus enumType
l
lawjolla
03/08/2019, 8:13 PMHey thanks @weakky! I'm struggling on the syntax. If I want to expose
Prisma Enum Copy code
const PrismaEnum = enumType({
name: "PrismaEnum"
});w
weakky
03/08/2019, 8:16 PM Copy code
prismaEnumType({
name: 'PrismaEnum',
members: ['value1', 'value2']
})weakky
03/08/2019, 8:16 PMJust a reminder though: You don’t need to declare it to have it exposed
weakky
03/08/2019, 8:17 PMThis is only useful if you want to hide members of the enum you defined in your datamodel
l
lawjolla
03/08/2019, 8:21 PMNexus is complaining that my Enums aren't imported from Prisma. There's something I'm not getting. That's normal. 🙂
w
weakky
03/08/2019, 8:22 PMTo what object type is that enum linked to ?
weakky
03/08/2019, 8:23 PMNexus-prisma works as follow: For all types that are missing, it’ll go look into the prisma schema and add it for you to your graphql api
l
lawjolla
03/08/2019, 8:30 PMOk, got it, thank you! The problem was sloppy code. I'm refactoring an old project that stitches in a third GraphQL API (that I also control).
I `graphql-import`ed all Prisma Enums, but as the project evolved, those Enums should have been moved out of Prisma and into the server. But I orphaned them in Prisma. That's why I was so confused... so to answer your question, they don't belong to a Prisma object type 🙂
🙌 1
4 Views