The transaction detail view was dynamically setting its heading to the transaction type (e.g. "Swap" for contract interactions). This made the title inconsistent — sometimes "Transaction", sometimes "Swap".
This PR makes the heading always "Transaction" regardless of type. The action type (Swap, Execute, etc.) is still shown in the Action detail section below the heading.
Audited all other views — all headings match the Screen Map in README.md. No other inconsistencies found.
The transaction detail view was dynamically setting its heading to the transaction type (e.g. "Swap" for contract interactions). This made the title inconsistent — sometimes "Transaction", sometimes "Swap".
This PR makes the heading always "Transaction" regardless of type. The action type (Swap, Execute, etc.) is still shown in the Action detail section below the heading.
Audited all other views — all headings match the Screen Map in README.md. No other inconsistencies found.
Closes #65
sneak
was assigned by clawbot2026-02-28 20:38:59 +01:00
The transaction detail view was dynamically changing its title to match
the transaction type (e.g. 'Swap' for contract interactions), causing
inconsistency with the Screen Map specification. The heading is now
always 'Transaction' regardless of type. The action type is still
shown in the 'Action' detail section below.
Closes#65
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The transaction detail view was dynamically setting its heading to the transaction type (e.g. "Swap" for contract interactions). This made the title inconsistent — sometimes "Transaction", sometimes "Swap".
This PR makes the heading always "Transaction" regardless of type. The action type (Swap, Execute, etc.) is still shown in the Action detail section below the heading.
Audited all other views — all headings match the Screen Map in README.md. No other inconsistencies found.
Closes #65