feat: match dashboard cost formatting and guardrail messages - #4
Merged
Merged
Conversation
Update formatCost to use the dashboard's autoDecimals behavior: values >= $1 are rounded to whole numbers, values < $1 show 2 decimal places. Rewrite formatGuardrailMessage to match the dashboard's buildTriggerReason, including scope, threshold explanations, and user message. This requires the new config fields added to GuardrailResult in go-proto.
owenrumney
approved these changes
Apr 1, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
formatCostto match the dashboard'sautoDecimalsbehavior: costs >= $1 are rounded to whole numbers, costs < $1 show 2 decimal placesformatCostChangeSentenceto useformatCostinstead of hardcodedStringFixed(2)formatGuardrailMessageto match the dashboard'sbuildTriggerReason— includes scope-based prefix, threshold explanations, total threshold, and user-configured messageBefore merging
This PR depends on infracost/go-proto#27 and currently points at a specific commit. Before merging:
go.modhere to point at the new tag instead of the commit hash