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
First of all thank you for such a great library and documentation.
I am facing a problem where my enums in POJOs have values that are not allowed in GraphQL enums (e.g. spaces):
publicenumMyEnum {
MY_FIRST_VAL("valid_value"),
MY_SECOND_VAL("invalid value with spaces");
}
Schemagen-graphql then fails at validating the values, when trying to convert those enum values to graphql enum values.
What I would like to achieve is to change the default behavior and treat my enums from POJOs as Strings in graphql schema, instead of treating them as explicit enums in graphql schema.
Is that achievable with a type mapper? Alternatively does anyone know of other workarounds?
The text was updated successfully, but these errors were encountered:
josemduarte
added a commit
to josemduarte/schemagen-graphql
that referenced
this issue
Jun 22, 2018
First of all thank you for such a great library and documentation.
I am facing a problem where my enums in POJOs have values that are not allowed in GraphQL enums (e.g. spaces):
Schemagen-graphql then fails at validating the values, when trying to convert those enum values to graphql enum values.
What I would like to achieve is to change the default behavior and treat my enums from POJOs as Strings in graphql schema, instead of treating them as explicit enums in graphql schema.
Is that achievable with a type mapper? Alternatively does anyone know of other workarounds?
The text was updated successfully, but these errors were encountered: