Configuration Options ===================== .. confval:: autoapi_dirs **Required** Paths (relative or absolute) to the source code that you wish to generate your API documentation from. For Python, if a package directory is specified, the package directory itself will be included in the relative path of the children. If an ordinary directory is specified, that directory will not be included in the relative path. .. confval:: autoapi_type Default: ``python`` Set the type of files you are documenting. This depends on the programming language that you are using: ========== ================ Language ``autoapi_type`` ========== ================ Python ``'python'`` Go ``'go'`` Javascript ``'javascript'`` .NET ``'dotnet'`` ========== ================ .. confval:: autoapi_template_dir Default: ``''`` A directory that has user-defined templates to override our default templates. You can view the default templates in the `autoapi/templates `_ directory of the package. .. confval:: autoapi_file_patterns Default: Varies by Language A list containing the file patterns to look for when generating documentation. The defaults by language are: ========== ============================================ Language ``autoapi_file_patterns`` ========== ============================================ Python ``['*.py', '*.pyi']`` Go ``['*.go']`` Javascript ``['*.js']`` .NET ``['project.json', '*.csproj', '*.vbproj']`` ========== ============================================ .. confval:: autoapi_generate_api_docs Default: ``True`` Whether to generate API documentation. If this is ``False``, documentation should be generated though the :doc:`directives`. Customization Options --------------------- .. confval:: autoapi_options Default: ``['members', 'undoc-members', 'private-members', 'special-members']`` Options for display of the documentation. * ``members``: Display children of an object * ``undoc-members``: Display objects that have no docstring * ``private-members``: Display private objects (eg. ``_foo`` in Python) * ``special-members``: Display special objects (eg. ``__foo__`` in Python) .. confval:: autoapi_ignore Default: Varies By Language A list of patterns to ignore when finding files The defaults by language are: ========== ============================================ Language ``autoapi_file_patterns`` ========== ============================================ Python ``['*migrations*']`` Go ``[]`` Javascript ``[]`` .NET ``['*toc.yml', '*index.yml']`` ========== ============================================ .. confval:: autoapi_root Default: ``autoapi`` Path to output the generated AutoAPI files into, including the generated index page. This path should be relative to the root of the documentation directory (ie the directory with the ``conf.py`` file). This can be used to place the generated documentation anywhere in your documentation hierarchy. .. confval:: autoapi_add_toctree_entry Default: ``True`` Whether to insert the generated documentation into the TOC tree. If this is ``False``, the default AutoAPI index page is not generated and you will need to include the generated documentation in a TOC tree entry yourself. .. confval:: autoapi_include_summaries Default: ``False`` Whether include autosummary directives in generated module documentation. This is a shortcut for needing to edit the templates yourself. .. confval:: autoapi_python_class_content Default: ``class`` Which docstring to insert into the content of a class. * ``class``: Use only the class docstring. * ``both``: Use the concatentation of the class docstring and the ``__init__`` docstring. * ``init``: Use only the ``__init__`` docstring. If the class does not have an ``__init__`` or the ``__init__`` docstring is empty and the class defines a ``__new__`` with a docstring, the ``__new__`` docstring is used instead of the ``__init__`` docstring. Debugging Options ----------------- .. confval:: autoapi_keep_files Default: ``False`` Keep the AutoAPI generated files on the filesystem after the run. Useful for debugging or transitioning to manual documentation.