Files
dawnline/rules/frontend.md
T
Aemeath 2f2aaf6c34
Build packages / CI (push) Blocked by required conditions
Build packages / Version (push) Waiting to run
CI / Web (format, types, tests, bundles) (push) Blocked by required conditions
CI / ShellCheck (push) Blocked by required conditions
CI / ucode static checks (push) Blocked by required conditions
CI / ucode compiles and tests pass (OpenWrt 24.10) (push) Blocked by required conditions
CI / ucode compiles and tests pass (OpenWrt 25.12) (push) Blocked by required conditions
Dawnline 0.11.0
- Russian translation. The admin pages, the LuCI menu and the router's
  messages (errors, Health checks, update steps, the service log) come in
  Russian with the new luci-i18n-dawnline-ru package, released beside the
  app. LuCI shows it when its language is Russian, or "auto" with a Russian
  browser
- The translation installs with install.sh when LuCI is in Russian (or with
  --lang ru), follows every Dawnline update and rollback, and can be added
  or removed in Components → Dawnline → Translation
- The portal speaks the visitor's language: it opens in the system's
  language and switches between English and Russian in place, from the
  language pill beside its QR code. It carries its own translation and needs
  no package
- Set-up steps quote the apps' own menus word for word, in Russian too:
  AmneziaVPN is "+ → Insert → Continue" (it has no "Add server"), and the
  Mac and Windows menus of WireGuard and AmneziaWG have their real names
- Questions in the portal (Reconnect, Remove) read from the left edge and
  close with Cancel, without ×
- Numbers, sizes and dates follow the page's language. A server that can't
  start says why in one sentence; event details and service log lines read
  as whole sentences
- README in Russian (README_ru.md). rules/i18n.md: how strings are written
  and translated; CI checks the catalogs (npm run i18n:check)
2026-10-20 19:33:52 +03:00

1.8 KiB

Frontend (TypeScript: admin UI and portal)

Read with code-standards.md and, for anything visible, ui-design.md and i18n.md (every visible string goes through _()).

Code

  • Strict TS, no any without a comment; types for RPC answers live in shared/types.ts / admin/api.ts and mirror the backend's shapes.
  • Layout of web/src/admin: ui/ generic components (button, menu, modal, drawer, tooltip, toast, controls), widgets/ composite house widgets, state/ polling and scoping, events/ the activity vocabulary (model without DOM, render separate), updater/ the Components data layer, cores/ per-protocol bits, pages/<page>/ one folder per page split by section, styles/*.css one file per feature joined in styles/index.ts. Shared with the portal: src/shared/.
  • Pages build from ui/ and widgets/; a page never defines a generic component. Logic that does not touch the DOM (formatting, models, CSV, sorting) lives outside the render code and gets tests.

Live data

  • Admin pages use createPoller (state/poller.ts): newest answer wins, no repaint of a region that holds focus, every RPC failure shows a toast or an inline error, never a blank section.
  • Changes reach open pages through the revision (state/live.ts): one small rev call every 2 s while the page is visible; pollers that opt in (live: true) refresh when it moves. Their own every stays as a slow fallback.
  • The portal does not poll (each request is a CGI process on the router, see backend.md): it loads once, after the visitor's own changes, and while it waits for a new device's first connection.

Checks

  • In web/: npm run format:check, npm run typecheck, npm run i18n:check, npm test, npm run build; the rebuilt bundles under package/ and the catalogs are committed (CI fails otherwise).