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
{{ message }}
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
I reuse custom types in my model class, for example a class called CreditCardNumber. Static fields in this class are also send with the request. On server side, the validation failed because of that static field is not defined in the schema.
public class CreditCardNumber {
private static final Pattern REGEX = Pattern.compile("\\d{12;19}");
private String number;
...
}
Because I share my custom types across different projects, I'm not able to annote the static field with @GraphQLIgnore.
How should I handle this? Is it a bug, that static fields are in included? May Mixins as used by Jackson be a possible solution?
The text was updated successfully, but these errors were encountered:
I have the same issue. Most of the model classes are reused across projects and they are all Serializable, thus causing the serialVersionUID to be included in the generated query. This fails validation because the serialVersionUID is not part of the schema. I have no control over the generated models and cannot put a @GraphQLIgnore annotation on this field.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I reuse custom types in my model class, for example a class called CreditCardNumber. Static fields in this class are also send with the request. On server side, the validation failed because of that static field is not defined in the schema.
Because I share my custom types across different projects, I'm not able to annote the static field with @GraphQLIgnore.
How should I handle this? Is it a bug, that static fields are in included? May Mixins as used by Jackson be a possible solution?
The text was updated successfully, but these errors were encountered: