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
Usage API: breakdownBy=creatorId #183
Usage API: breakdownBy=creatorId #183
Changes from 6 commits
47cabdd
3df29e0
240398b
1fa41e6
beb4ff9
8454c26
cfb89ab
c5ee4ae
21cdd32
5a94d8c
30b94f4
9d9dcea
1c50458
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.
Should we have a separate check for when we have breakdown vs when we don't? When we don't have any breakdown there should be only 1 result, so it'd be an error to have more results
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.
This change from
*UsageSummaryRow
to[]Metric
is another breaking change. If a client was calling this API before and parsing the response as an object, it will now explode cause it's getting an array.My suggestion is to build on top of the
QuerySummary
vsQuerySummaryWithTimestep
separation, given the latter already returns an array. So, instead of changing every response to be an array, we could changeQuerySummaryWithTimestep
to beQuerySummaryWithBreakdown
instead and update the check here to also call the breakdown version whenlen(breakdownBy) > 0
. And then we leave the no-breakdown version still returning an object not to break any existing integrations. WDYT?