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 your feature request related to a problem? Please describe.
I'd like to implement what this library currently does with relayConfig but for any custom type. It's currently possible to tell the generator that a graphql type (e.g. UserConnection) should be defined as an hardcoded class with a generic. I would like this possible for any type since I want to use the TypeDefinitionConfigurer from spring-graphql (https://docs.spring.io/spring-graphql/docs/1.2.2/reference/html/#execution.pagination.types). graphql-java-tools has something similar too.
Describe the solution you'd like
My goal here would be to define something like this: type Mutation { participateToQuiz(quizId: Int!): ParticipationPayload @payload(for: "Participation") }
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I haven't identified alternative solutions to achieve the desired functionality.
I'm more than happy to implement this feature myself and would appreciate feedback on its feasibility and acceptance.
Thanks !
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'd like to implement what this library currently does with
relayConfig
but for any custom type. It's currently possible to tell the generator that a graphql type (e.g.UserConnection
) should be defined as an hardcoded class with a generic. I would like this possible for any type since I want to use theTypeDefinitionConfigurer
from spring-graphql (https://docs.spring.io/spring-graphql/docs/1.2.2/reference/html/#execution.pagination.types). graphql-java-tools has something similar too.Describe the solution you'd like
My goal here would be to define something like this:
type Mutation { participateToQuiz(quizId: Int!): ParticipationPayload @payload(for: "Participation") }
Then in the plugin configuration:
This would then define the following resolver interface:
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I haven't identified alternative solutions to achieve the desired functionality.
I'm more than happy to implement this feature myself and would appreciate feedback on its feasibility and acceptance.
Thanks !
The text was updated successfully, but these errors were encountered: