Console: Invalid error shown for multiple top level fields in subscription
See original GitHub issueThe following query shows an error in the GraphiQL console “Subscription xyz must select only one top level field”.
subscription xyz {
abc { id },
pqr { id }
}
However, the query works fine when executed.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Error handling - Apollo GraphQL Docs
The GraphQL operation includes an invalid value for a field argument. ... In the examples below, we use top-level await calls to start...
Read more >Top GraphQL Errors and How to fix them
Top GraphQL Errors and How to Fix them. Error handling in GraphQL is different on both server and client side tooling.
Read more >Troubleshoot Subscriptions - Tableau Help
If you receive a subscription with this error message, there could be several reasons: Missing credentials: Some views are published with embedded ...
Read more >Resolve template validation or template format errors in ...
I receive an error message when I try to create my AWS CloudFormation ... For "Invalid template property or properties [XXXXXXXX]" errors, ...
Read more >Common errors | Content API for Shopping - Google Developers
[link] validation/invalid_value for <destinations> : URLs do not belong to your website. quota/too_many_items: Merchant quota exceeded. The ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@hrj Unfortunately, multiple top level fields are not a part of the GraphQL subscription spec: https://facebook.github.io/graphql/draft/#sec-Single-root-field
Commenting here - I have a need to retrieve the total count of a particular query, but also provide pagination using
limit
andoffset
. With a normal query I can simply remove the offset/limit portion of the arguments, but with I’ve found thataggregate.count
will return the total count constrained to thelimit
that’s set - is there a way to accomplish this with limiting queries but still return the total count of the full query?