feat(rounding): Expose rounding attributes to APIs #2764
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vincent-pochet
force-pushed
the
feat-rounding-api
branch
from
0e3eafe
to
f30c8f5
Compare
vincent-pochet
force-pushed
the
feat-rounding-fields
branch
2 times, most recently
from
ecf0b6d
to
aae776b
Compare
vincent-pochet
force-pushed
the
feat-rounding-api
branch
from
f30c8f5
to
840a6d6
Compare
This was referenced Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
In addition to the flexible aggregation, some customers wants to round the output of the aggregation.
Description
This PR exposes
rounding_functionandrounding_precisionfields to REST and GraphQL APIs. It also updateBillableMetrics#CreateServiceandBillableMetrics#UpdateService