Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOCS: Adopt autoapi v3 for our API doc generation. #5708

Open
tkknight opened this issue Jan 22, 2024 · 2 comments
Open

DOCS: Adopt autoapi v3 for our API doc generation. #5708

tkknight opened this issue Jan 22, 2024 · 2 comments

Comments

@tkknight
Copy link
Contributor

📚 Documentation

We currently use apidoc for our API Docs, which look like this: https://scitools-iris.readthedocs.io/en/latest/generated/api/iris.html.

Autodoc headline:

Sphinx AutoAPI is a Sphinx extension for generating complete API documentation without needing to load, run, or import the project being documented.

In contrast to the traditional Sphinx autodoc, which requires some manual authoring and uses code imports, AutoAPI finds and generates documentation by parsing source code.

I have locally trialed using autoapi which generally is:

  • presented better
  • uses the autosummary for modules and classes (table summary)

There is a build warning that can be resolved with some investigation but the main issue blocking the adoption is the use of inline comments to document attributes using #: str: this is a comment before the attribute is defined. autoapi works using the triple quotes after the attribute is defined but this would mean changing lots of comments already present and it is limited to a single line.

Lets watch readthedocs/sphinx-autoapi#344 to see if support for #: comments is added, if so we can look at adopting autoapi.

@bjlittle
Copy link
Member

@tkknight Should this pull-request be in draft?

@bjlittle
Copy link
Member

@tkknight doh! my mistake, this is an issue, all good 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants