[unstable option] format_code_in_doc_comments
Open
Nobody has claimed this yet.
S-tracking-blocking-bugs
unstable-option
UO-format_code_in_doc_comments
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 24
Description
Tracking issue for unstable option: format_code_in_doc_comments
Contributor guide
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.
Research direction
Start by reviewing the tracking issue for the unstable format_code_in_doc_comments option and its discussion. The payload names no source files, tests, or entry points, so first identify the implementation and expected formatting behavior before work can be scoped. Done would require a decided design and completed support for the option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100