[checks] Check for `in \xrefc`
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- tex
- Domain
- tooling
Research direction
Start by reviewing the examples in pull request 9318 and locating the existing checks that validate xrefc usage. Add coverage for the pattern "in \xrefc"; done means both mistaken instances are detected by the check.
Written by the indexing model from the issue text.
Description
As seen in https://github.com/cplusplus/draft/pull/9318, there are some instances where \xrefc was mistakenly used like \ref, but it's a standalone element with a SEE ALSO preamble.
Both instances could have been prevented by checking for in +\\xrefc.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
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 cplusplus/draft
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
P2-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
P2-Bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
P2-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hemilabs/ui-monorepo#2332 ·
-
Help-Wanted Needs-Triage Package-Update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/winget-pkgs#438662 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
olcf/olcf-test-harness#278 · 1 comment ·