Annotate inherited documentation as such
Open
- Dominant language
- C++
- Stars
- 340
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
e.g., what we do for "(implicit)" etc.
Contributor guide
Research direction
No file or test is named. Start by locating the code that emits inherited documentation and the existing "(implicit)" annotation behavior; done means inherited documentation is consistently identified as such, including the implicit case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, jekyll
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100