-
Notifications
You must be signed in to change notification settings - Fork 192
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
Add automatically generated API doc #1242
Comments
I'll see whether I can get rid of some of the most prominent problems... then at some point other people will need to help. |
Didn't know that existed, but sounds like a great plan. Just tag me if you open PR or a branch and need help with fixing docstrings |
I'll be working on this here: https://github.com/ltalirz/aiida_core/tree/issue_1242_sphinx-apidoc If it's like usual, then most of these will be simple formatting problems. |
@sphuber I'm now down to 42 warnings For reference, here are the warnings
|
Excellent, I will see if I can take a look soon, thanks |
I have had a look and fixed a bunch of errors. We are now down to 3, that I don't really now how to fix.
The second and third are import errors. They come from the restapi and alembic (SqlAlchemy migrations). Maybe you know about the first and we can ask Spyros about the latter. The first warning is due to an internal error that we raise related to testing in |
@sphuber Thanks a bunch, this is moving forward much faster than I expected! The restapi error looks like a typo (should be
@waychal |
This work continues in PR #1330 |
#1330 merged |
While working on #1228 I noticed that basic classes like
Group
orUser
were not part of the module guide.I suggest we use sphinx-apidoc to produce an automatically generated & complete API documentation.
Probably, quite a few of the
docs/source/.../dev.rst
files can be removed (even though in some cases there may be some value in selecting subset of the actual documentation).The text was updated successfully, but these errors were encountered: