ArduPilot / ArduPilot/MAVProxy
Link Connection Types "udpin" and "updout" to "UDP Client" and UDP Server"
- Dominant language
- Python
- Stars
- 595
- Forks
- 773
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 18
Description
I think it would be better to rename the "udpin" and "updout" Connection types to the more standard "UDP Client" and "UDP Server" nomenclature. It's not a huge deal but for people who are new to networking (including myself) the non-standard words make me stop and pause and wonder which is which.
Similarly "tcpin" and "tcp" should probably be renamed to "TCP Server" and "TCP Client" respectively
Contributor guide
No contributing guide indexed for this repository
Research direction
Search the MAVProxy codebase for the connection types "udpin", "updout", "tcpin", and "tcp" and inspect where their user-facing names are defined. Confirm how each maps to UDP Client, UDP Server, TCP Server, and TCP Client, then verify that the renamed labels appear consistently wherever these connection types are shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100