Repository navigation
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
❌ Deploy Preview for explorer-cash failed.
|
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
explorer | f8b7e58 | Nov 15 2026, 03:02 AM |
salemkode
force-pushed
the
fix/13-compact-token-badges
branch
from
November 14, 2026 20:18
ebb1e07 to
15f7b2a
Compare
salemkode
force-pushed
the
fix/13-compact-token-badges
branch
from
November 15, 2026 02:56
15f7b2a to
f8b7e58
Compare
This was referenced Nov 15, 2026
This branch has not been deployed
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
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.
Transaction token badges compact display amounts after applying metadata decimals while preserving exact decimal values, original base units, and commitments in accessible disclosures and copy controls. The issue #26 reported amount 72624976668144285 and 9223372036854775807 retain every digit. Integration isolates the real Vue/registry/BaseCopy component fixture in a child process and supplies the Nuxt shims it needs; its original component assertions are retained.
Addresses #13.
This PR keeps base
mainand descends from cleanup commit4cd0fb6c2fe09a60dfbf6889fa7b67d72c23a949. Immediate prerequisite: PR #33. Manual merge order: #32 → #33 → #37. These prerequisites are included in the current diff until they are merged.Focused comparison against the immediate prerequisite. Documentation: README.md. Feature-specific documentation uses separate files so independent branches do not append competing README sections.
Validation at
f8b7e58bf2de1585becd664f92e4cdf4c63b41a2: compatible dependencies installed withbun install --frozen-lockfile;bun run lint;bun test(87 top-level passing tests, including subprocess component suites); every test file run individually;bun run lint:type(actual GraphQL document validation/codegen against the unchanged checked-in schema and Nuxt typecheck);bun run build;git diff --check. All passed. No dependencies or backend/schema changes.The complete eleven-issue aggregate also passes lint, codegen/typecheck, static build, every test file individually, and 425 top-level tests including the preserved exact badge/component suites. Independent merge paths after #32: #33 → #37; #35 → #38 → #40 → #39 → #42 → #41; #34 → #43; #36 independently. All PR bases remain
main.Limits: this integration pass used deterministic query/reactive/component fixtures. No interactive browser, focus/layout, clipboard, real-wallet, or live-indexer verification was performed. Prior independent review findings were implemented and regression-tested; the independent reviewers have not re-reviewed these rewritten heads. Existing hook messages reported missing lefthook; no safeguard or hook was bypassed. No PR was merged and no issue was closed.
Remote check status after the integration push: GitHub Validate explorer / validate passed on this exact head. Netlify deploy-preview plus its Pages/Header/Redirect checks failed; the same failures also occur on unchanged PR #32, #33 and #36. GitHub’s output says only “Deploy failed”; the public deploy metadata reports
errorwithout a build-cause message. This integration does not claim Netlify is green and does not change cleanup PR #32. The separate Cloudflare check may finish independently.