The list of dependencies of an integration on the doc page should be automatically generated #311

New Issue

Closed

opened 2023-09-02 12:17:12 +02:00 by blacklight · 0 comments

blacklight commented

2023-09-02 12:17:12 +02:00

Owner

We should therefore only keep the manifest as the source of truth, and the dependencies should be dynamically parsed from the manifest when the Sphinx docs are built.

It takes quite some effort to write down the same dependencies of an integration in its manifest file, in the docstring of its class and in the extras of the setup.py - and keep all these places aligned. We should therefore only keep the manifest as the source of truth, and the dependencies should be dynamically parsed from the manifest when the Sphinx docs are built.

blacklight added the

enhancement

documentation

labels 2023-09-02 12:17:12 +02:00

blacklight self-assigned this 2023-09-02 12:17:12 +02:00

blacklight added this to the core project 2023-09-02 12:17:12 +02:00

blacklight changed title from ~~The list of dependencies of an integrations on the doc page should be automatically generated~~ to The list of dependencies of an integration on the doc page should be automatically generated

2023-09-02 12:17:49 +02:00

blacklight referenced this issue from a commit

2023-09-24 17:00:30 +02:00

[#311] Docs deps autogen sphinx plugin.

~~blacklight referenced this issue 2023-09-24 17:02:16 +02:00~~

[#311] Logic to automatically generate the documentation for the dependencies of the integrations #330

blacklight added reference 311/auto-generate-deps-docs

2023-09-24 17:02:41 +02:00

blacklight referenced a pull request that will close this issue

2023-09-24 17:03:32 +02:00

[#311] Logic to automatically generate the documentation for the dependencies of the integrations #330

blacklight closed this issue