-
Currently API documentation is a bit poor and some sections are empty (like Main loop). It might be very confusing for new users.
I propose to add a paragraph explaining general purpose of main parts…
-
-
We should document the Open311 api as we've implmented it. We have a small number of additions and deviations from the Open311 specification.
It would probably make the most sense to do the document…
-
```
I like the philosophy behind Closure, but I'd like to make a few comments
regarding the API documentation:
- When you read the source code, TabPane is deprecated, but that's not
indicated in th…
-
Need to write a full documentation of all API endpoints.
See #253 for how this fits in with testing and refactors, which should be done together.
#### Documentation needed:
All [routes.js](https://g…
-
Create API documentation on server side
-
The README does not provide enough information about the API endpoints. Things like:
- Type of parameter
- Is this parameter optional or required?
-
Hello fellow @hoaproject/hoackers and users!
Related RFC: #51, #52, and #53.
The API documentation is a mess, and useless. Not specifically in Hoa, but in the majority of PHP projects. Recently,…
Hywan updated
7 years ago
-
The API documentation needs to be updated with all the new functionality recently added. This includes the Solarsoft and SunPy science download script generation.
-
### Feature request
I really appreciated https://docs.bentoml.com/en/latest/guides/testing.html#unit-tests. It would be helpful to include also docs on mocking the bentoml decorated API methods.
…
smidm updated
1 month ago