Ben MeadorsandGitHub
bbe9a0d5cd
* feat(protobufs): sync to firmware-current and consume workspace package Sync the vendored .proto sources to firmware-current (v2.7.25+48), regenerate the v2 TS bindings, and consume the workspace @meshtastic/protobufs (workspace:*) in place of the stale JSR 2.7.20 — finishing the monorepo migration (core was already workspace:*). Includes the one required breaking-change fix: admin nodedb_reset changed int32 to bool, so resetNodes() now sends value: true. * build(protobufs): vendor generated bindings for workspace consumers The package is consumed via workspace:* — its exports point at the TS source, which imports ./dist/meshtastic/*_pb.ts — so the generated output must exist at build time. CI builds web/core with no codegen step and the runners have no buf CLI, so the bindings are vendored here (kept gitignored; lint/format skip them). Regenerate with: pnpm --filter @meshtastic/protobufs gen * fix(protobufs): clean script removes the actual generated output dir buf writes bindings to packages/ts/dist, but clean was removing a non-existent root dist — so it never cleaned stale output. Addresses Copilot review feedback. * refactor: move web app packages/web -> apps/web Aligns the web app with the apps/web layout (matching the Vercel web-test Root Directory and the SDK-migration direction). Pure directory move plus root config: pnpm-workspace (adds apps/*), vitest projects, root tsconfig reference, and the pr/release-web/nightly workflows. vercel.json moved with the app. Build + 36 validation tests green. * feat: config fields, module pages, key verification, telemetry capture Incorporates the firmware-current feature work onto the protobuf foundation: new config fields (Display message bubbles; LoRa fem_lna_mode + serial_hal_only; Telemetry air_quality_screen_enabled); 4 new ModuleConfig pages (TrafficManagement, StatusMessage, TAK, RemoteHardware); the manual Key Verification flow (sendKeyVerification + ClientNotificationDialog stages + Verify Key button); live telemetry capture (nodeDB addDeviceMetrics) and admin hardening (toggleMutedNode, graceful PortNum default); plus the sdk-preview ConfigEditor demo and store/config tests. Build + lint + format + 131 tests green. * chore: drop #1062 (unsaved-change-detection) to match upstream revert #1062 was merged to main by accident (per @danditomaso) and is being reverted. Reverse-applied its diff here via 3-way so #1097 stays consistent with where main is headed, while keeping the feature changes layered on the same files (deviceStore/changeRegistry). Build + 131 tests + lint + format green. * fix(nodes): clean up SNR display in node table and map popup SNR is a ratio measured in dB, not dBm (which is absolute power); the node table and map popup both mislabeled it and crammed three values together: '0dBm/50%/50raw'. The trailing '%/raw' pair was the same heuristic ((snr+10)*5) shown twice — once clamped, once not. Render SNR in dB rounded to one decimal, color-coded by a 0-100% signal-quality heuristic (green/yellow/red), with the quality percentage as a muted secondary. Drop the redundant raw value. Adds unit.db; this matches the existing SNRTooltip, which already renders dB.
32 lines
1.4 KiB
Markdown
32 lines
1.4 KiB
Markdown
# Contributing Translations
|
|
|
|
Thank you for your interest in making the Meshtastic Web Client accessible to a
|
|
global audience! Your translation efforts are greatly appreciated.
|
|
|
|
## Our Translation Platform: Crowdin
|
|
|
|
We manage all our translations through a platform called
|
|
[Crowdin](https://crowdin.com/). This allows for a collaborative and streamlined
|
|
translation process. All translation work should be done on our Crowdin project,
|
|
not directly in the code repository via Pull Requests.
|
|
|
|
### How to Get Started
|
|
|
|
1. **Create a Crowdin Account:** If you don't already have one, sign up for a
|
|
free account on Crowdin.
|
|
2. **Join Our Project:** Please ask for a link to our specific Crowdin project
|
|
on the Meshtastic Discord.
|
|
3. **Request Translator Role:** Once you have an account, join the Meshtastic
|
|
Discord and notify an admin in the `#web` channel. They will grant you the
|
|
necessary permissions to start translating.
|
|
4. **Start Translating:** Once you have your role, you can begin translating the
|
|
source labels into your native language directly on the Crowdin platform.
|
|
|
|
### Language Activation
|
|
|
|
A new language will only be added to the web client and appear in the language
|
|
picker once its translation is 100% complete on Crowdin. The repository
|
|
maintainers will handle this process once the milestone is reached.
|
|
|
|
Thank you for helping us bring Meshtastic to more users around the world!
|