Closed ysavourel closed 5 years ago
I would prefer to have one universal way how to filter collections based on it's parameters, and that is as you mentioned:
I suppose we could have GET /tasks?jobId={jobId} but currently it's not defined.
This is related to https://github.com/GALAglobal/TAPICC-API-implementation/issues/35
Unfortunately it seems there is no way currently to define global query parameters in swagger definition. We would have to add them manually to each route. So I wonder if we should do it in swagger definition (add all possible query params for filtering and sorting in each route) Or have some single declaration in some external documentation.
Now that tasks are decoupled from assets (per issue OAI/OpenAPI-Specification#47), it's not clear how we can access tasks .
GET /tasks
but that gives you all the tasks across all jobs, I'm not sure anyone would want to get that list (and it could get rather long).tasks
list in each asset object, but that won't account for task not associated to an asset.I suppose we could have
GET /tasks?jobId={jobId}
but currently it's not defined. Should we haveGET /jobs/{jobId}/tasks
?