Closed demariadaniel closed 6 months ago
just a comment. might be worth using the returned entity names from the query instead of the parsed request entity names. frontend can submit anything and there seems to be minimal error checking on the entity parts of this code (there are thrown errors for invalid programs)
as we discussed on slack - endpoint is array of strings but our use case is ok for a single name in the filename as we don't download multiple files (eg. a filename with 14 diff entity names)
just a comment. might be worth using the returned entity names from the query instead of the parsed request entity names. frontend can submit anything and there seems to be minimal error checking on the entity parts of this code (there are thrown errors for invalid programs)
Sounds good, insures names are standardized, protects against edge cases: https://github.com/icgc-argo/argo-clinical/pull/1098/commits/3f2caaf06dd5eb977b5ef3f8c38f22e94822fb26
Description of changes
Type of Change
Checklist before requesting review:
develop
not master)validationDependency
in meta tag for Argo Dictionary fields used in code