api_pages
frequenz.repo.config.mkdocs.api_pages ¤
Generate the code reference pages.
It uses the following mkdocs plugins:
mkdocs-gen-filesto generate the API documentation pages.mkdocs-literate-navto make use of the generateSUMMARY.mdfile.
Based on the recipe at: https://mkdocstrings.github.io/recipes/#automatic-code-reference-pages
Functions¤
frequenz.repo.config.mkdocs.api_pages.generate_protobuf_api_pages ¤
generate_protobuf_api_pages(
src_path: str = "proto",
dst_path: str = "protobuf-reference",
) -> None
Generate API documentation pages for the code.
Internal modules (those starting with an underscore except from __init__) are
not included.
A summary page is generated as SUMMARY.md which is compatible with the
mkdocs-literary-nav plugin.
| PARAMETER | DESCRIPTION |
|---|---|
src_path
|
Path where the code is located.
TYPE:
|
dst_path
|
Path where the documentation should be generated. This is relative to the output directory of mkdocs.
TYPE:
|
Source code in frequenz/repo/config/mkdocs/api_pages.py
frequenz.repo.config.mkdocs.api_pages.generate_python_api_pages ¤
Generate API documentation pages for the code.
Internal modules (those starting with an underscore except from __init__) are
not included.
A summary page is generated as SUMMARY.md which is compatible with the
mkdocs-literary-nav plugin.
| PARAMETER | DESCRIPTION |
|---|---|
src_path
|
Path where the code is located.
TYPE:
|
dst_path
|
Path where the documentation should be generated. This is relative to the output directory of mkdocs.
TYPE:
|