You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very useful if the API automatically generated using sphinx's autodoc is included in the documentation of readthedocs. If I understand correctly this was actually the plan (#1 (comment)). Still I think it is good to have a github issue requesting this.
Just for reference. I am considering the use of ruyaml to generate a yaml with comments (omni-us/jsonargparse#52). But the methods that can be used to add comments are not documented. There is only one example in the documentation which only mentions yaml_add_eol_comment but there is no way to know what other methods there are or the parameters they receive and their descriptions.
The text was updated successfully, but these errors were encountered:
indeed i was very suprised that this (or rather the origin) so popular package has such a, excuse my dutch, shitty documentation. it would be most helpful not only to add API docs, but also to get rid of all the contents with elaborations about a previous API and whatnot anecdotes.
It would be very useful if the API automatically generated using sphinx's autodoc is included in the documentation of readthedocs. If I understand correctly this was actually the plan (#1 (comment)). Still I think it is good to have a github issue requesting this.
Just for reference. I am considering the use of ruyaml to generate a yaml with comments (omni-us/jsonargparse#52). But the methods that can be used to add comments are not documented. There is only one example in the documentation which only mentions
yaml_add_eol_comment
but there is no way to know what other methods there are or the parameters they receive and their descriptions.The text was updated successfully, but these errors were encountered: