-
Notifications
You must be signed in to change notification settings - Fork 18
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
File endpoint #25
File endpoint #25
Conversation
- name: type | ||
required: true | ||
in: path | ||
description: The output type of the descriptor. If not specified it is up to the underlying implementation to determine which output type to return. Plain types return the bare descriptor while the "non-plain" types return a descriptor wrapped with metadata. Allowable values are "CWL" and "WDL". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is returning an array of ToolFile, so this description (especially the part about plain types) seems off
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing...
items: | ||
$ref: '#/definitions/ToolFile' | ||
'404': | ||
description: The tool can not be output in the specified type. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might have been copied and not changed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe the error is for when somebody puts an unknown descriptor type in the path parameter. Even though the tool exists, the tool can not be output in the specified type. Using WDL on a CWL tool on the other hand does not trigger a 404, only a 204.
properties: | ||
path: | ||
type: string | ||
description: Relative path of a file that can be used with the GA4GH .../{type}/descriptor/{relative_path} endpoint if the file is a primary or secondary descriptor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What can be done with the dockerfile and test files? (as a question that comes up when reading this and could be useful to document)
Introduces a new endpoint to display relative paths of all files for #20
Provides a better description for #21 and #22