Philip Reiner Kensche

Results 21 comments of Philip Reiner Kensche

I would be interested in this feature as well. I try to implement a DB update function that needs to deal with concurrent modifications. The DB we use (MongoDB) does...

There is only a next-page token field. Generally, when paging, and in particular with 10000+ tasks, you may want to avoid to having to iterate through all pages. Did you...

Right, I can also not see now how one could ensure that only the tasks of the specific workflow run are being displayed, because this would have to be embedded...

Note that adding an optional field in an expected request is backwards compatible. In a response, however, a simple non-optional field may also be considered backwards compatible, if it is...

Not sure whether I should open a new issue or just add my comments here. I'll do the latter. There is this "freeze" request by @susheel . Could he maybe...

The missing 1.0.1 version tag issue is clearer covered in #191. Semantic versioning is also covered in #71. I don't see what other topics of this issue are not better...

## Inputs First concerning the input **formats**: I think, the current restriction of the format of `workflow_params` to JSON should be dropped. There are just too many formats (YAML, JSON,...

@mr-c I'm unsure what you mean by "standardized schema". Do you mean the format, such as JSON? Or do you mean like a JSON schema? My guess is that you...

My comment assumed that the WES API would enforce as little from the workflow engines and workflows as possible. Therefore I tried to find a solution that satisfies this assumption....