fix(frontend): nft asset count and usage health exclude#1493
Merged
Conversation
… than 0"
The NFT assets grid header bypassed the shared count helpers, always
rendering the "More than {{count}}" string via numberFormat. An empty
account therefore showed the nonsensical "More than 0 NFT assets found".
Use the same standard every other table uses: isApproxCount() to pick
total vs totalExact and countFormat() for grouping. Exact counts
(including 0) now read "A total of N NFT assets found".
Health-check endpoints are high-volume probe noise that shouldn't count toward third-party API usage stats. Add /v1/health to SKIP_PREFIXES alongside the existing legacy/sync exclusions.
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
1 participant
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.
No description provided.