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
The way this module makes or identifies collection by checking if the name consists "Collection" keyword. But Some APIDOC authors might prefer Drones instead of DroneCollection. In order to parse APIDOCs not written using doc_writer, we need to have more general way of identifying classes and collection.
I'm submitting a
Current Behaviour:
The way this module makes or identifies collection by checking if the name consists "Collection" keyword. But Some APIDOC authors might prefer Drones instead of DroneCollection. In order to parse APIDOCs not written using
doc_writer
, we need to have more general way of identifying classes and collection.The entrypoint of the APIDOC used in the Hydra-CG uses the
hydra:collection
to identify the collections: https://github.com/HydraCG/cookbook/blob/master/api-documentation/1.entry-point.mdAlso related discussion on the spec repo related to this:
HydraCG/Specifications#126
Related Issues on Agent:
HTTP-APIs/hydra-python-agent-gui#7
HTTP-APIs/hydra-python-agent-gui#43
Expected Behaviour:
The module would be able to parse classes and collections in more general way.
Do you want to work on this issue?
yes
The text was updated successfully, but these errors were encountered: