check_explainer_count.py finds the ROADMAP table cell by column position
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 80/100
Research direction
Start in scripts/check_explainer_count.py, where the regex counts leading columns to find the Explainers cell in the ROADMAP Current traction table. Change it to read the header row, locate the Explainers column by name, and take that cell from the next data row. Done when a test that adds a column before Explainers still reads the correct cell.
Written by the indexing model from the issue text.
Description
Where: scripts/check_explainer_count.py.
Current gap: The regex for the Current traction table's Explainers cell counts the eight leading columns, so adding or reordering a column makes it match the wrong cell or nothing.
Suggested approach: Read the header row, find the Explainers column by name and take that cell of the next data row.
Done when: a test adds a column before Explainers and the check still reads the right cell.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 3h 24m
- Merged PRs (30d)
- 101
Getting set up
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 yakew7/Fair-Code
-
enhancement good first issue tooling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
ci community enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
The pre-commit hooks lack the issue-reference, traction and contributors checks that make lint runsOpenenhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug community tooling
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
ci-rerun: collect.py fails a whole pr-babysit cycle on one transient GitHub 5xx and never retriesOpenfollow-up
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
chore: remove unused Stripe billing env varsPossibly taken @anshikasharmaa1517 claimed this today. Open🐛 bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
area/frontend area/v2 kind/bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
REditorSupport/languageserver#833 ·
Maintainers usually reply within 1 day
-
cmd/ebitenmobile: multi-language bindings run the complete generator twicePossibly taken @kumagi claimed this today. Openos:macos performance
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hajimehoshi/ebiten#4011 · 1 comment ·
Maintainers usually reply within 1 day