In the current behaviour, when the fields is passed it replaces the previous set configuration of fields (structural design of runs components). Since there will be multiple implementation of WES and TES which might not be compliant, it might be a good idea to give the feature of extending default config rather than always replacing it.
Possible solution(s)
Add extends API(prop) to ecc-client-litga4gh-tes-runs and ecc-client-lit-ga4gh-wes-runs, and now when the app-author passes extends=true the fields passes should extend the default fields/config.
If I understand this correctly, this makes sense even for compliant implementations, because the GA4GH API specs generally do not prohibit additional properties in their models.
Description
In the current behaviour, when the fields is passed it replaces the previous set configuration of fields (structural design of runs components). Since there will be multiple implementation of WES and TES which might not be compliant, it might be a good idea to give the feature of extending default config rather than always replacing it.
Possible solution(s)
Add
extends
API(prop) toecc-client-litga4gh-tes-runs
andecc-client-lit-ga4gh-wes-runs
, and now when theapp-author
passesextends=true
thefields
passes should extend the default fields/config.