-
-
Notifications
You must be signed in to change notification settings - Fork 389
Add documentation to plugins #2066
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I added a document in the call hierarchy, maybe we can let this as an example. |
Of course! many thanks, i think we should ask for something similar for the new plugins (and work hard to add it for the existing ones) |
We have to do a check list here with the plugins and the current status of their docs |
The actual features doc page could link to each plugin as suggested by @michaelpj , once their docs are completed (or gradually while the plugins are being completed) |
👍 to this. We have some readmes already, it would be great to have more! I'd also like to incorporate them into the doc build properly... perhaps I can symlink them in so that sphinx will index them as part of the main project? 🤔 |
The plugins now have some more documentation, just on the features page. There could be a lot more, though. |
I updated the state by my personal search, not sure if contains all. #2066 (comment) |
This looks completed to me, thank you everyone! |
-Wredundant-imports
for remove unused imports) #2064), kown issues, etcThe text was updated successfully, but these errors were encountered: