[#311] Logic to automatically generate the documentation for the dependencies of the integrations #330
No reviewers
Labels
No Label
architecture
bug
ci/cd
cleanup
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
new feature
packaging
question
ui
waiting user input
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: platypush/platypush#330
Loading…
Reference in New Issue
No description provided.
Delete Branch "311/auto-generate-deps-docs"
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?
Added an
add_dependencies
plugin to the Sphinx build process that parses the manifest files of the scanned backends and plugins and automatically generates the documentation for the required dependencies and triggered events.This means that those dependencies are no longer required to be listed in the docstring of the class itself.
Also in this commit:
Black/LINT for some integrations that hadn't been touched in a long time.
Deleted some leftovers from previous refactors (deprecated
backend.mqtt
,backend.zwave.mqtt
,backend.http.request.rss
).Deleted deprecated
inotify
backend - replaced byfile.monitor
(see #289).Closes: #311, #318