http-apis.github.io icon indicating copy to clipboard operation
http-apis.github.io copied to clipboard

HydraEcoSystem.Org - Main documentation entrypoint for Hydra Ecosystem's tools.

Results 7 http-apis.github.io issues
Sort by recently updated
recently updated
newest added

In the Usage page of the Documentation (http://www.hydraecosystem.org/01-Usage) the "add_supported_class" method contains two arguments `apidoc.add_supported_class(class_, collection=True)` where as in the doc_writer.py there in no such collection agrument required. ![image](https://user-images.githubusercontent.com/49719371/104067504-46ce6400-5229-11eb-8cf1-f50752c0e4f7.png)

In the Usage page of the Documentation (http://www.hydraecosystem.org/01-Usage) the "get_classes" method contains python dictionary as an argument `doc_parse.get_classes(apidoc.generate())` But the get_class method requires the HydraDoc object as argument. ![image](https://user-images.githubusercontent.com/49719371/104068109-60bc7680-522a-11eb-9b52-8a8a6b3dcb25.png)

Since documentation can contain many sub-sections, sometimes it's difficult to share some specific section. It can be resolved by ensuring proper indexing of all the sub-sections. This can make navigating...

Currently, at [hydra core](https://github.com/HTTP-APIs/hydra-python-core) we have very little usage documentation on how to interact with the Hydra Doc. Also, we have almost no references to it around the documentation as...

good first issue

A lot of new changes in `hydra-python-core` and the `hydrus` server have not been incorporated in the docs yet. This really confuses a new user when he is going through...

The documentation is maintained in a manner that is un-structured. Building a UI that helps structure the documentation as well as using a better generator for the same can help...