Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Aggregated queries #1 #8345
Aggregated queries #1 #8345
Changes from 26 commits
4b51b58
3f929c9
49bc25a
10fdfd5
6b3e533
3fb0fe0
7adb8ce
ad441bd
fe53fb8
cd4465f
d26a1bd
870fc61
dc72de9
d3dbf46
52e8a88
55ce64d
f8d4c2a
5af68f8
db02867
2c6549a
b347f39
6ca4628
7c7ee44
22d0fb9
b182252
2d7ff9c
fce5c81
c1df0e5
765d9a6
e5a9e3d
b44ceb9
1aee63c
853126a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logic: skipping non-edges fields when edges exist could prevent aggregation fields from being processed at the root level
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we replace totalCount everywhere in the app by countUniqueId? We'll need to give a heads up for deprecation but we can start replacing it in our frontend at least. We plan to email people about API Key deprecation so we can let them know about this at the same time.
If I'm not mistaken we're doing a separate query for totalCount now while this could fit in the same query with all other aggregated fields?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logic: removing 'totalCount' and 'pageInfo' from shouldNotParseField may cause these fields to be incorrectly included in the select statement