Allow autosummary to create pages for classes, functions, etc

[ZedThree]

Subject: Allow autosummary to create pages for classes, functions, and so on

Feature or Bugfix

• Feature

Purpose

As detailed in #7912 and linked issues, autosummary is very useful and with a small tweak is incredibly powerful for generating complete API docs for a project.

The solution here is perhaps a little hacky, but it builds on the templates proposed in #7912, with an escape-hatch for projects where this solutions causes more issues. The new option autosummary_recurse_members (strawperson name) basically just controls whether :toctree: is set in the template or not:

   .. autosummary::
   {%- if recurse_members %}
      :toctree:
   {% endif %}

This new option defaults to True so that users get this out of the box -- but this was just my preference.

In the class template, the :inherited-members: setting is also guarded to respect autodoc_inherit_docstrings. I'm not sure if the I've implemented this in the correct way, but it does seem to work.

Relates

• By default, make Autosummary templates generate documentation pages for classes, functions, exceptions etc #7912