Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Do not generate documentation for rule family if it does not contain any | David Chen | 2016-02-17 |
| | | | | | | | | | | | | | | documented rules. Currently, we are generating an empty page for the Protocol Buffer rules on bazel.io because the rule definition exists but all the rules are set as undocumented. In cases like these, the docgen should neither generate a page nor any links for the rule family. Fixes #882 -- MOS_MIGRATED_REVID=114834947 | ||
* | Refactor BuildEncyclopediaProcessor to use a common RuleFamily class for rule | David Chen | 2015-12-16 |
documentation passed to templates. * This simplifies the logic in BuildEncyclopediaProcessor, reducing the number of various different data structures we use for generating different pages. * This also makes RuleFamily more similar to the BuildLanguage proto, which we we may consider using in the future for the native rule docgen since the Skylark docgen will be using BuildLanguage. -- MOS_MIGRATED_REVID=110265727 |