Sabela
Sabela
Well, I think that for the top level error (those which prevent the Beacon from giving a response) the HTTP status code provided in the response should be the same...
I've just talked to @silverdaz and got a new porposal. Returning a 200 when some non-blocking-error has happened is not good BUT there are other 2xx codes (or even 4xx)...
You're right, but maybe this could be improved. I mean, one of the errors that could happen is that the user sends an `assemblyId` and a `datasetId` which do not...
Example of the response when there are 2 datasets and one of them has detected an error: ```json [ { "beaconId": "some-beacon", "apiVersion": "v1.0.1", "exists": true, "alleleRequest": { "referenceName": "1",...
mmm I don't agree :P If the user knows the assemblies do not match, they can choose to convert the `start` position to the other coordinate system. If they just...
I think that if you request a dataset which does not exist, you should fill the top level `error` in `BeaconAlleleResponse` and nothing else. ```json [ { "beaconId": "some-beacon", "apiVersion":...
Regarding the 1st bullet point: I'm not sure I understood you. The HTTP status code will always be 200 unless there is an error while doing the call (3xx) or...
I created PR #267 which implements issue #262 and tries to clarify what we are discussing here.
I totally missed this last comment. And I'm also confused, probably because we're having the very same discussion in different issues and PRs. I think we should continue in #267...
I created PR #267