Epic: YARD API Documentation Migration #92
Labels
No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference: aethyr/Aethyr#92
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Metadata
chore(docs): migrate from RDoc to YARDfeature/yard-migrationBackground and Context
The specification lists YARD as the API documentation tool, but the codebase currently
uses RDoc (
rdoc ~> 4.2in gemspec,Rake::RDocTaskin Rakefile). YARD providesricher documentation features including
@param,@return,@raisetags,cross-references, and better HTML output.
Expected Behavior
All API documentation is generated by YARD. The
yardgem replacesrdocas adependency. The Rakefile uses
YARD::Rake::YardocTask. Existing doc comments areconverted to YARD's
@tagformat.Acceptance Criteria
yardgem replacesrdocin gemspecYARD::Rake::YardocTask@tagformatrake yardgenerates documentation successfullySubtasks
Definition of Done
This Epic is complete when all child issues are closed and all acceptance criteria
are satisfied.