We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug A query which doesn't specify any subfields on a non-scalar field should be rejected.
To Reproduce
Run the following SQL:
create table account( id serial primary key, email varchar(255) not null ); select jsonb_pretty(graphql.resolve($$ query { accountCollection } $$));
Observe that the above GraphQL query returns:
jsonb_pretty ----------------------------------- { + "data": { + "accountCollection": null+ } + } (1 row)
Expected behavior The query should be rejected with an error message because the accountCollection field has id and email sub-fields.
accountCollection
id
email
Screenshots If applicable, add screenshots to help explain your problem.
Versions:
The text was updated successfully, but these errors were encountered:
olirice
No branches or pull requests
Describe the bug
A query which doesn't specify any subfields on a non-scalar field should be rejected.
To Reproduce
Run the following SQL:
Observe that the above GraphQL query returns:
Expected behavior
The query should be rejected with an error message because the
accountCollection
field hasid
andemail
sub-fields.Screenshots
If applicable, add screenshots to help explain your problem.
Versions:
The text was updated successfully, but these errors were encountered: