Sphinx-Needs provides an open API for other Sphinx-extensions to provide specific need-types, create needs or make usage of the filter possibilities.
The API allows the injection of extra configuration, but does not support manipulation of it (e.g remove need types), to keep the final configuration transparent for the Sphinx project authors.
.. automodule:: sphinx_needs.api.configuration :members:
.. autoclass:: sphinx_needs.functions.functions.DynamicFunction :members: __name__,__call__
.. automodule:: sphinx_needs.api.need :members:
.. automodule:: sphinx_needs.exceptions :members:
.. automodule:: sphinx_needs.need_item :members: NeedItem, NeedPartItem, NeedItemSourceProtocol, NeedsContent, NeedPartData, NeedModification, NeedConstraintResults
.. automodule:: sphinx_needs.data :members: NeedsInfoType, NeedsInfoComputedType, NeedsSourceInfoType, NeedsMutable, NeedsPartType
These views are returned by certain functions, and injected into filters, but should not be instantiated directly.
.. automodule:: sphinx_needs.views :members: :undoc-members: :special-members: __iter__, __getitem__, __len__
.. automodule:: sphinx_needs.needs_schema
:members: FieldsSchema, FieldSchema, FieldFunctionArray, LinksFunctionArray,
FieldLiteralValue, LinkSchema, LinksLiteralValue, AllowedTypes
.. automodule:: sphinx_needs.schema.config
:members: ExtraOptionStringSchemaType, ExtraOptionBooleanSchemaType,
ExtraOptionIntegerSchemaType, ExtraOptionNumberSchemaType,
ExtraOptionMultiValueSchemaType