Render DNF and DNS instead of raw negative result sentinels
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Locate the result formatter used by the competition result tables and inspect where values enter event-specific formatting. Add focused regression coverage for -1 and -2, verifying DNF and DNS while preserving normal centisecond, FMC, Multi-Blind, and zero-value placeholder behavior.
Written by the indexing model from the issue text.
Description
Problem
Competition result values use WCA sentinel values for non-results:
-1meansDNF-2meansDNS
The current result formatter passes these values through numeric event formatting, so result tables can display the raw values -1 and -2. This is visible in the Lipnica Wielka Open 2026 results screenshot.
Expected behavior
Every displayed attempt, best, average, or mean result should render the WCA status text instead of the sentinel number:
-1->DNF-2->DNS
Acceptance criteria
- Negative WCA result sentinels are handled before event-specific formatting.
-1renders asDNF.-2renders asDNS.- Normal centisecond, FMC, and Multi-Blind result formatting remains unchanged.
- Existing zero-value placeholder behavior remains unchanged.
- Add focused regression tests for both sentinels.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 12
- Avg merge
- 34m
- Merged PRs (30d)
- 2
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 coder13/Competitor-groups
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
coder13/Competitor-groups#85 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
coder13/Competitor-groups#82 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
coder13/Competitor-groups#72 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
coder13/Competitor-groups#30 ·
-
coder13/Competitor-groups#27 · 1 reaction · 1 assignee ·
All issues in coder13/Competitor-groups
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100