Add support to enums on message variables

Open
#201 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
networking, tooling

Research direction

Review the repository's message definitions and code-generation utilities first. Identify how variable values are currently represented and documented, then determine the expected representation for enum values. Done means enum values are supported consistently rather than only described in comments; the issue names no specific files or tests.

Written by the indexing model from the issue text.

Description

Some messages could use enum as valid values and not defined values in comments.

Dominant language
Python
Stars
27
Forks
26
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bluerobotics/ping-protocol

All issues in bluerobotics/ping-protocol

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.