The list of dependencies of an integration on the doc page should be automatically generated #311
Labels
No labels
architecture
authentication
backend
bug
ci/cd
cleanup
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
media
mobile
new feature
packaging
question
ui
voice
waiting user input
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: platypush/platypush#311
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
The list of dependencies of an integrations on the doc page should be automatically generatedto The list of dependencies of an integration on the doc page should be automatically generatedblacklight referenced this issue2023-09-24 17:02:16 +02:00