-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add operationId for all HCA DSS endpoints #2720
Comments
@dvantwisk this repository has been in a maintenance only mode for a couple of months (Nov 2019), it appears that the current DSS is getting depreciated, and replaced with something else. I'm not sure how long that processing is going to take, but if possible I'll make the changes to the |
@dvantwisk the changes have to propagate their way up.... see #2724; ill let you know when it lands to the production env: https://dss.data.humancellatlas.org/v1/swagger.json |
Hello,
I am using the
swagger-generator
api generator to access the HCA DCP DSS API. This creates a series of functions that can be easily generated in R and the list of functions looks as follows:Here the
hca
object has these functions created by the api generator available. It can be seen that some names are long and unwieldy likeFind_bundles_by_searching_their_metadata_with_an_Elasticsearch_query
. Others make a lot more sense such asdss.api.bundles.checkout.get
. This is because the api generator names for functions first after theoperationId
tag in the https://dss.data.humancellatlas.org/v1/swagger.json document. If the tag is not present for an endpoint, the name defaults to thesummary
tag. Some endpoints in theswagger.json
document have theseoperationId
tags while others do not, thus causing this issue.I ask that appropriately named
operationId
tags be added to all endpoints in the document.The text was updated successfully, but these errors were encountered: