Repository navigation
Improve argument coloring where available - #743
Conversation
* Use %(default)s where appropriate * Otherwise, use backticks around default values * Use backticks when referring to console commands, such as references to other command line options or example command invocations
d6b7d9b to
48ed3a0
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #743 +/- ##
==========================================
- Coverage 87.66% 87.60% -0.07%
==========================================
Files 74 75 +1
Lines 4442 4581 +139
Branches 771 797 +26
==========================================
+ Hits 3894 4013 +119
- Misses 433 445 +12
- Partials 115 123 +8 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Works fine, nothing breaks. Ran the tests locally, flake8 and spell check pass, coverage unchanged.
One thing that looks like it slipped through:
verb/test.py:93 and :98 - the --build-base / --install-base args there are identical to the ones in verb/build.py (same wrap_default_value() defaults), but they still say (default: build) / (default: install). So colcon build --help gets the coloring and colcon test --help doesn't.
Rest LGTM 👍
|
Ah, well caught @PiousCrossten! I've addressed this in b2008de. |
Example with Python 3.15:

Note that we're not actually choosing the palette here, we're just giving
argparsethe information it needs to align with other console output.