-
Notifications
You must be signed in to change notification settings - Fork 8
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
Some API entries are empty #23
Comments
Following, most functions in the API - Foxes Documentation page are empty. Any plans to update this? If adding specific introduction is too much a workload you may consider copying doc strings of each class such as class FarmController(FarmDataModel): ... to the API documentation. For each package(e.g. core), there should also include a few sentences on its high-level functionalities. For documentation at least input and return parameters should be included in the docs. linking openjournals/joss-reviews#5464 for tracking review progress. |
Thanks for the remark (I was sick for two weeks, hence the late reply - sorry). The documentation is generated by All classes docu is fine, reflecting the foxes sub-package structure in the API. Is my fixing this bug required for the publication? It's tedious.. Thanks again! |
Thanks for your update! Hope you have fully recovered. A complete documentation(both class-level and function-level) are generally required for the publication. I'm not very familiar with using sphinx together with readthedocs but based on your description have you tried checking project module path(E.G. If this is caused by sphinx package itself you may try raising an issue under the sphinx-doc repo. Some references:
|
Great, thanks for the links! I will try to fix this issue with these hints. |
Fixed in new version v0.3.5 (now |
I will close this issue now, since the problem described here is solved. @isdanni feel free to re-open if you have doubts, thanks |
These API entries are empty:
Maybe because these are variables/functions, not classes?
The text was updated successfully, but these errors were encountered: