Repository navigation
Cost: write just "≥" when an amount is both a lower bound and partly estimated - #387
Merged
Merged
Conversation
…estimated "≥" already says the figure is not exact; the estimated part stays in the hover. Overview and session costs share one costPrefix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When some requests could not be priced and the rest include estimates, costs were prefixed with "≥~". "≥" alone already marks the amount as not exact, and the estimated share is still spelled out in the hover and the cost detail row, so the prefix is now just "≥". "~" stays for amounts that are only estimated.
costPrefixmoves tosrc/traffic/costCell.tsand is shared by the overview (tile, distribution, breakdown, past year, tooltips) and session costs in Traffic.🤖 Generated with Claude Code