-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
static
fields shouldn't be added to Types & Inputs
#700
Comments
Hi @ybroeker ! Welcome back :) This is a valid point ! Are you looking to fix this ? |
ybroeker
added a commit
to ybroeker/smallrye-graphql
that referenced
this issue
Mar 31, 2021
ybroeker
added a commit
to ybroeker/smallrye-graphql
that referenced
this issue
Mar 31, 2021
ybroeker
added a commit
to ybroeker/smallrye-graphql
that referenced
this issue
Mar 31, 2021
refs smallrye#700, refs smallrye#701 Signed-off-by: Yannick da Silva Bröker <[email protected]>
ybroeker
added a commit
to ybroeker/smallrye-graphql
that referenced
this issue
Mar 31, 2021
…a field and/or method as a graphql field.
phillip-kruger
added a commit
that referenced
this issue
Mar 31, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently,
static
fields are added to the schema on types and inputs, which means constants must be explicitly ignored.Those fields should be ignored by default.
Especially for inputs, as these field cannot be used at runtime.
The text was updated successfully, but these errors were encountered: