Diagnostic reporting should use some fancy color formatting
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
Research direction
Start by reading the AssertionChecker and tracing where its diagnostic items are written. Define the expected colorized output and the flag that disables it; done means diagnostics use color escape sequences when enabled and remain uncolored when disabled.
Written by the indexing model from the issue text.
Description
We have this really nice diagnostic tooling in the AssertionChecker, but writing the diagnostic items should use some fancy escape characters to color code the output (but we also probably should allow that to be disabled via a flag, too).
- Dominant language
- Zig
- Stars
- 11
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bradcypert/httpspec
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
bradcypert/httpspec#12 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bradcypert/httpspec#11 ·
All issues in bradcypert/httpspec
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·