Skip to content

feat(explorer): clarify transaction type and address flow - #199

Merged
moscowchill merged 1 commit into
devfrom
feat/transaction-flow
Sep 22, 2026
Merged

moscowchill merged 1 commit into
devfrom
feat/transaction-flow

Conversation

@moscowchill

Copy link
Copy Markdown
Contributor

Summary

  • Add a neutral transaction-type pill and a responsive From-to-To flow on transaction details.
  • Preserve full address links and copy values, receipt status, exact fee display, and existing address-page IN/OUT labels.
  • Keep factory-call recipients distinct from child contracts and represent unavailable metadata conservatively.

Validation

  • 631 Jest tests across 48 suites passed.
  • Lint: no errors; 14 existing warnings. TypeScript and API-doc drift checks passed.
  • Production build passed with the unrelated hosted dApp prebuild skipped locally.
  • 31 production-browser checks passed, including 14 new transaction-flow cases and 17 existing explorer UI regressions.
  • Phone and desktop, light and dark screenshots visually reviewed using synthetic fixtures.
  • Independent source review: no blocking findings; 22 focused tests independently passed.
  • Prettier passed for new files, tests, and fixture changes. The existing transaction renderer has baseline formatting drift; unrelated formatting was preserved.

Risks and scope

  • Presentation-only changes. No backend, network, wallet, balance, or signing behavior changed.
  • Transaction type remains independent from execution status. Missing or inconclusive metadata uses a neutral label.
  • Pending transactions retain their existing dedicated page.
  • Production deployment is separate from this integration PR.

@moscowchill
moscowchill merged commit d045d5b into dev Sep 22, 2026
3 checks passed
@moscowchill
moscowchill deleted the feat/transaction-flow branch September 22, 2026 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant