Review and possibly upstream `sdoc`'s RDoc patches
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 930
- Forks
- 465
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 27
Description
sdoc being one of the major users of rdoc has patches to workaround issues/enhance features, which @jonathanhefner compiled in this comment. We should review them and adopt the ones that make sense for rdoc users in general.
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 reading the sdoc patch list in the linked comment on pull request #1330 and compare each proposal with RDoc's current behavior. Determine which patches benefit RDoc users generally; done means the applicable changes are agreed, implemented, and validated with relevant checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100