feat(logging): let operators log every supported mode (JS8/FST4/Q65/…), not just 8

[patrickrb]

Problem

Both logging forms — the dashboard Quick Log card and the full New Contact page — hard-coded the same 8-entry mode menu:

SSB · CW · FT8 · FT4 · RTTY · PSK31 · AM · FM

Meanwhile the rest of the app has moved past that list:

• Search now offers the full canonical mode list (feat(search): offer every stored mode in the mode filter (JS8/FST4/JT65/Q65/Olivia/…) #242) — JS8, FST4, JT65, JT9, Q65, MSK144, PSK63, Olivia, Contestia, the digital-voice modes, etc.
• ADIF import promotes a WSJT-X/fldigi SUBMODE to the stored mode (feat(adif): store the ADIF submode (FT4/JS8/PSK31) as the QSO mode on import #240), so a JS8 or Q65 run lands in the log as JS8/Q65.

The result was a drift: an operator could import and filter those modes, but could not log one directly. Working a JS8 or Q65 station from the dashboard meant picking the wrong mode and fixing it after the fact. This is exactly the class of hard-coded-list-drift the search filters were fixed for in #241/#242.

Solution

• Both forms now source their mode menu from the canonical AMATEUR_MODES (src/lib/modes.ts) — precisely the way they already source their band menu from AMATEUR_BANDS. Every mode the log can store is now loggable, and the list can never fall behind import/search again.
• The per-mode RST default (599 for CW, a dB-style -10 for the digital families, 59 otherwise) was duplicated across the two forms with two subtly different, incomplete copies. It's now a single defaultRstForMode(mode) helper in the canonical modes module. The classification is preserved exactly for every mode both forms already handled, and extended to the newly loggable digital modes (JS8, FST4, JT65, JT9, Q65, MSK144, PSK63).

No new options were removed — all 8 legacy modes remain, in the same lead position (SSB/CW/FT8/FT4 stay at the top of the list). The menus are ordered common-first, so the everyday phone/CW modes are still the first thing an operator sees.

Behavior note

On the New Contact page, selecting a mode that fell outside the old three if branches (e.g. DMR) previously left the RST untouched; it now resets to 59, matching what the Quick Log card already did. This makes the two forms consistent and is a sensible default for digital-voice/image modes.

Testing

• npm run typecheck — clean
• npm run lint — clean
• npm run build — succeeds
• npx playwright test tests/modes.spec.ts — 12 passed, including new defaultRstForMode coverage (CW→599, phone→59, dB modes→-10, digital-voice/image→59, case-insensitivity, backward-compat with the pre-centralization classification, and a default for every canonical mode).

Future follow-up

• The dB-style -10 default currently also covers RTTY/PSK/MFSK/Olivia/Contestia. That's preserved from the prior behavior (not necessarily conventionally correct — RTTY/PSK operators often send RST), and could be revisited separately if desired.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nodelog	Ready	Preview, Comment	Jul 24, 2026 9:08am