docs: document the 1.44 features that were never written up - #141
Merged
kelsos merged 2 commits intoAug 24, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Twelve features shipped in 1.44 with no mention anywhere in the docs. All verified against the v1.44.0 tag. The notification area had never been documented at all, so silencing popups had nowhere to live. It gets a section in utilities covering the area itself, the tabs, the silence toggle and its persistence, the back-off schedule for a condition that keeps recurring, and clearing. Settings entries: auto detect tokens on login and its 1-168 hour cooldown; suppressing the "No indexers available" notification per chain and where to undo it; the recommended-settings dialog shown after an upgrade changes a chain's default indexer; and the integrity checks now run in both directions of a premium cloud sync. Feature mentions: Hyperliquid Core tokens as first class assets keyed by token ID; Gnosis Pay Safe migration detection and which address to add; jumping from a rule to the events it governs and back; and asset search by contract address with exact matches first, on both the dashboard and blockchain balances. The calendar's automatic-entry list named only ENS. It was missing five other categories besides the Yearn vesting escrow entries new in 1.44, so it now lists all of them, with ENS widened to the name services it actually covers (ENS, Basenames and .gwei). The filter bar rolled out to nine more tables in 1.44 but only history events documented it. Rather than repeat that page nine times, address book, oracle prices and accounting rules each get a short section naming the pills that page offers, pointing at the canonical reference for the shared syntax. Also correct where the directory entries live: Logs Directory and Data Directory are in the desktop app's own menu bar, not the in-app ? menu, so they are documented on the data directory page with a pointer from help.
VitePress checks that a linked page exists but not that the #anchor on the end of it does, so renaming a heading silently breaks every link pointing at it. That has now happened twice here. Two links in premium/index.md still pointed at #creating-api-keys and #using-api-keys-in-the-app after those headings became "API Credentials", and the app's importAddressBook deep link pointed at a heading slug that had never existed. Both were found by hand; nothing would have caught the next one. Add scripts/check-anchors.mjs, wired in as pnpm run check:anchors and a CI step. It slugs headings the way VitePress does (lowercase, every run of non-alphanumerics collapsed to one hyphen) and fails on any internal link whose anchor matches no heading on the target page. Verified against a deliberately broken link before trusting the green result. Then fix the two links it found.
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.
Second of three PRs catching the docs up to 1.44. PR 1 (#140) fixed pages that
described a UI 1.44 had replaced; this one adds the twelve features that were
never documented at all. Screenshots are still PR 3.
Everything verified against the v1.44.0 tag. Three things came out different
from what the changelog implied — flagged below.
New sections
The notification area (utilities/index). It had never been documented,
so 1.44's silence-popups feature had nowhere to live. Covers the area and its
four tabs, the silence toggle and the fact that nothing is lost while it is
on, the back-off schedule for a condition that keeps recurring (immediately,
a day, two days, a week, then quiet), and clearing.
Filter bar on three more pages. 1.44 rolled the pill bar out to nine
tables but only history events documented it. Rather than repeat
history/filtering nine times, address book, oracle prices and accounting
rules each get a short section naming the pills that page actually offers and
pointing at the canonical reference for the shared syntax.
Settings
cooldown, 1 to 168 hours, which only appears when the toggle is on and
which a manual re-detect ignores.
chain, and where to undo it.
a chain's default indexer, and what it shows for Gnosis.
both directions (premium/sync.py on upload, data_handler.py on the
downloaded copy).
Feature mentions
than a contract address. The string "Hyperliquid" previously appeared
nowhere in the docs.
on the dashboard and on blockchain balances.
Three corrections to the plan, from reading the code
The calendar list was missing far more than the new entries. It named only
"ENS Expiration & Renewal". tasks/calendar.py has six creators: name service
expiry (now covering ENS, Basenames and .gwei, not just ENS),
airdrop claim deadlines, Yearn vesting escrow cliff and full-vest (new in
1.44), CRV vote escrow, VELO/AERO veNFT escrow, and L2 bridging. All six are
now listed.
Logs Directory and Data Directory are not in the in-app ? menu. They are
in the Electron application menu bar's Help menu (electron/main/menu.ts),
which is a different menu with different entries. Documenting them on
utilities/help would have been wrong, so they are on the data directory page
— where someone looking for that folder actually goes — with a pointer from
help. Also notes that Data Directory stays disabled until the backend is up,
and that neither exists when running through Docker in a browser.
Two internal links were already broken. Auditing anchors to confirm PR 1's
page split was safe turned up premium/index.md still linking to
#creating-api-keys and #using-api-keys-in-the-app after those headings
became "API Credentials".
Anchor gate
VitePress validates that a linked page exists but not that its #anchor does,
so a renamed heading breaks inbound links silently. That has now happened
twice — the two above, plus the app's importAddressBook deep link fixed in
PR 1. Both were found by hand and nothing would have caught the next one.
scripts/check-anchors.mjs slugs headings the way VitePress does and fails on
any internal link whose anchor matches no heading on the target page. Wired in
as pnpm run check:anchors and a CI step, alongside the image gate from PR 1.
Verified with a negative control — deliberately reintroduced a broken link and
confirmed the gate fails on it — rather than trusting the green result.
Verification
pnpm run lint, check:images, check:anchors and build all clean.
58 anchored internal links across 71 pages all resolve.