Skip to content

docs: add settings validation reference#5218

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/generate-validation-documentation
Draft

docs: add settings validation reference#5218
Copilot wants to merge 2 commits into
mainfrom
copilot/generate-validation-documentation

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 22, 2026

Comprehensive reference documenting the validation rules enforced on every radio config and module config settings screen, sourced from both protobuf max_size annotations and the UI form layer.

  • Device config screens (User, Device, Position, Power, Network, Display, LoRa, Bluetooth, Security) — per-field type, constraint, and conditional visibility rules
  • Module config screens (MQTT, Serial, Ext Notification, Store & Forward, Range Test, Telemetry, Canned Message, Audio, Remote Hardware, Neighbor Info, Ambient Lighting, Detection Sensor, Paxcounter, Status Message, Traffic Management, TAK) — same treatment
  • Channel config — name byte limit, PSK length constraints (0/16/32 bytes)
  • Interval configurations — all 17 IntervalConfiguration contexts with their exact allowed value sets in seconds
  • UI component validation — documents how each reusable core:ui component (EditTextPreference, DropDownPreference, EditIPv4Preference, EditBase64Preference, BitwisePreference, SliderPreference, etc.) enforces constraints

Example entry:

Field Type Validation Notes
long_name String maxSize: 39 bytes (proto max_size: 40) Required (non-blank)
latitude Double Range: −90.0 to +90.0 Visible only when fixed_position = true
fixed_pin String Exactly 6 digits

Also notes known discrepancies (e.g. allow_input_source UI enforces 63 bytes while proto specifies max_size: 16).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants