Enforce disallowed comment characters across all types
CBielstein opened this issue · comments
Description
Currently, only StatusInfo
and MaidenheadBeaconInfo
correctly enforce disallowed characters in an ARPS message comment (|
or ~
). This should be consistent across all packets which support a comment.
Acceptance Criteria
- Check user-specified comments for disallowed characters across all packet types (consider not enforcing for decoded packets, just for sending)
- Find a way to reduce duplication.