You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to transform the outputs which pal g creates in both the typeDefs and resolvers outputs? For example, our existing setup has resolvers defined in this format in our schema.graphql (using a type named User as an example):
type Query {
users(first: Int, skip: Int, where: UserWhereInput): [User]!
}
type Mutation {
createUser(data: UserCreateInput!): User!
updateUser(data: UserUpdateInput!, where: UserWhereUniqueInput!): User
deleteUser(where: UserWhereUniqueInput!): User
}
However I noticed that pal g will create these in the format (I know there are other queries that are also generated such as findUniqueUser, findFirstUser, etc. , but just scoping on the specifics for now):
Is there any config that I can provide to "transform" the names of the created resolvers - and more importantly the typeDefs - into the formats that fit our current system?
We already have something in place which will handle the execution of the resolvers, the main goal is for us to dynamically generate our schema.graphql on our current schema.prisma files, hence the importance on the typeDefs.
The text was updated successfully, but these errors were encountered:
Is it possible to transform the outputs which
pal g
creates in both thetypeDefs
andresolvers
outputs? For example, our existing setup has resolvers defined in this format in our schema.graphql (using a type namedUser
as an example):However I noticed that
pal g
will create these in the format (I know there are other queries that are also generated such asfindUniqueUser
,findFirstUser
, etc. , but just scoping on the specifics for now):Is there any config that I can provide to "transform" the names of the created
resolvers
- and more importantly thetypeDefs
- into the formats that fit our current system?We already have something in place which will handle the execution of the resolvers, the main goal is for us to dynamically generate our schema.graphql on our current schema.prisma files, hence the importance on the
typeDefs
.The text was updated successfully, but these errors were encountered: