Map code to docs, consider automating testing of code in docs #1636
Labels
Priority: High
Very important task, not blocking but potentially delaying milestones or limiting our offering
Type: Documentation
Improvements or additions to documentation
Milestone
Adam and I agreed it would be worthwhile to identify all of the code our docs reference so we may ensure updates to one are at least considered for the other. To this end, I have created this mapping:
https://app.golinks.io/code2docs
It identifies .move and .toml files referenced in (and typically linked from) the docs. The goal is to insert a code comment near the top helping the requisite engineer find the associated docs. I have proposed the syntax in the doc above yet welcome refinement.
Related, Francois is suggesting use of this to test Rust-specific references:
https://github.com/budziq/rust-skeptic
The text was updated successfully, but these errors were encountered: