Thanks for providing an openapi.json file to describe the REST API. I am trying to auto-generate a client based on the contents of the openapi.json. In my previous projects the method names were derived from the operation id but unfortunately there is no operation Id in the openapi.json in this repo.
It would be great if you could add it so that I do not need to fall-back to the summary which leads to method names like CreateAnAttributeWithNameAttrAndAssignItToHDF5ObjectObjuudi for the REST path PUT /{collection}/{obj_uuid}/attributes/{attr}. The operation ID for that path could be CreateAttribute or create_attribute.
Thanks for providing an
openapi.json
file to describe the REST API. I am trying to auto-generate a client based on the contents of theopenapi.json
. In my previous projects the method names were derived from the operation id but unfortunately there is no operation Id in theopenapi.json
in this repo.It would be great if you could add it so that I do not need to fall-back to the
summary
which leads to method names likeCreateAnAttributeWithNameAttrAndAssignItToHDF5ObjectObjuudi
for the REST pathPUT /{collection}/{obj_uuid}/attributes/{attr}
. The operation ID for that path could beCreateAttribute
orcreate_attribute
.Thank you :-)