Skip to content

Fix API reference page so all functions render - #502

Merged
sgosline merged 1 commit into
mainfrom
docs-api-reference-render
Oct 6, 2026
Merged

sgosline merged 1 commit into
mainfrom
docs-api-reference-render

Conversation

@jjacobson95

@jjacobson95 jjacobson95 commented Sep 28, 2026 •

Copy link
Copy Markdown
Collaborator

Documentation Update #2


Merge this second.

The API Reference page only displayed the download function; every other function was missing.

Root cause: autodoc_typehints in docs/source/conf.py was set to a list (["none"]) instead of a string. That made Sphinx's typehints handler raise on the first documented object, silently truncating the rest of the page. A second issue: APIreference.rst listed plot_2D_respones_metric with the wrong casing, so that function was never picked up.

Changes:

  • autodoc_typehints = "none" (string, as Sphinx requires)
  • correct the stats function name to plot_2d_respones_metric in APIreference.rst

Verified via the docs workflow: the build succeeds (it was failing on main) and the rendered API page now lists all Dataset/loader/stats functions.

Closes #475

autodoc_typehints must be a string, not a list; the list value made
Sphinx's typehints handler raise on the first documented object, which
silently truncated the API Reference to only the download function.
Also correct the stats function name casing in APIreference.rst
(plot_2d_respones_metric) so it is picked up by autodoc.
@jjacobson95 jjacobson95 added the documentation Improvements or additions to documentation label Sep 28, 2026
@jjacobson95 jjacobson95 added this to the 2.4 Documentation milestone Sep 28, 2026

@sgosline sgosline left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you just review the docs and make sure we're merging to the correct branch? I know the docs page has its own branch and I dont want to mess things up

@jjacobson95

Copy link
Copy Markdown
Collaborator Author

Yes, confirmed this is the right way to do it. All of the docs changes go to main (and this will fix the actions once all merged), and then I'll sync documentation-staging with main and it will rebuild. And then future updates will be managed again with documentation-staging - which should generally stay up to date or ahead of main.

documentation-staging will mainly be used for testing docs changes without having to commit to main, but right now is broken (and fixed in #503).

@sgosline
sgosline merged commit 2c93f3c into main Oct 6, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs Site API Reference Page is Not Rendering Correctly

2 participants