Found by a deployability verification of next at 75a5fa9, observed in a real browser.
The testnet banner renders the internal view id to the user: [TESTNET] (approve-tx). Written deliberately at src/popup/views/helpers.js:122, and it applies to the DEBUG banner too.
Useful while developing, but it is internal vocabulary on a user-facing banner, and on the approval screen it sits directly above the text stating what is being authorized — where every other word has been carefully chosen this milestone.
Definition of done
The view id does not appear in a user-facing banner in a release build.
If it is wanted for development, it survives only in a debug build — note make build-debug already distinguishes the two and script/verify-build enforces which is which.
make check green.
Found by a deployability verification of `next` at `75a5fa9`, observed in a real browser.
The testnet banner renders the internal view id to the user: `[TESTNET] (approve-tx)`. Written deliberately at `src/popup/views/helpers.js:122`, and it applies to the DEBUG banner too.
Useful while developing, but it is internal vocabulary on a user-facing banner, and on the approval screen it sits directly above the text stating what is being authorized — where every other word has been carefully chosen this milestone.
## Definition of done
- [ ] The view id does not appear in a user-facing banner in a release build.
- [ ] If it is wanted for development, it survives only in a debug build — note `make build-debug` already distinguishes the two and `script/verify-build` enforces which is which.
- [ ] `make check` green.
The banner no longer shows the internal view id in a release build. The suffix that produced text like [TESTNET] (approve-tx) is now gated on the compile-time DEBUG constant rather than isDebug() (which is also true for a testnet or the runtime debug toggle), so it survives only in a debug build; a testnet or the runtime toggle still raises the banner, just without the view id.
The banner no longer shows the internal view id in a release build. The suffix that produced text like `[TESTNET] (approve-tx)` is now gated on the compile-time `DEBUG` constant rather than `isDebug()` (which is also true for a testnet or the runtime debug toggle), so it survives only in a debug build; a testnet or the runtime toggle still raises the banner, just without the view id.
PR: https://git.eeqj.de/sneak/AutistMask/pulls/389
Model: opus-4-8
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.
Found by a deployability verification of
nextat75a5fa9, observed in a real browser.The testnet banner renders the internal view id to the user:
[TESTNET] (approve-tx). Written deliberately atsrc/popup/views/helpers.js:122, and it applies to the DEBUG banner too.Useful while developing, but it is internal vocabulary on a user-facing banner, and on the approval screen it sits directly above the text stating what is being authorized — where every other word has been carefully chosen this milestone.
Definition of done
make build-debugalready distinguishes the two andscript/verify-buildenforces which is which.make checkgreen.The banner no longer shows the internal view id in a release build. The suffix that produced text like
[TESTNET] (approve-tx)is now gated on the compile-timeDEBUGconstant rather thanisDebug()(which is also true for a testnet or the runtime debug toggle), so it survives only in a debug build; a testnet or the runtime toggle still raises the banner, just without the view id.PR: #389
Model: opus-4-8