--> Some (maybe all?) Errors from the initial Validation step can no longer be parsed properly, and a Normalization layer needs to be in place between the Service and rendered UI to somehow normalize them in some way. <---
[Bill]-- The results from the validation endpoint have already been normalized, so no need to add a normalization layer, just use the new normalized format. Coordinate with Gesina @ PSC about the format.
https://github.com/hubmapconsortium/ingest-api/tree/main/src/routes/validation
The Information here is not entirely accurate; the responses look very different when they contain errors. There are numerous kinds of errors that can return and all of them seem to be wrapped up differently. I don't know the different variations we can expect; Is there Documentation on smartAPI or the Hubmap API page (Note: Noticed the link to ingest API's github instead links to ingest UI's) that breaks down the different kind of errors we can expect?
Created from ISSUE #1417
--> Some (maybe all?) Errors from the initial Validation step can no longer be parsed properly, and a Normalization layer needs to be in place between the Service and rendered UI to somehow normalize them in some way. <--- [Bill]-- The results from the validation endpoint have already been normalized, so no need to add a normalization layer, just use the new normalized format. Coordinate with Gesina @ PSC about the format.
https://github.com/hubmapconsortium/ingest-api/tree/main/src/routes/validation The Information here is not entirely accurate; the responses look very different when they contain errors. There are numerous kinds of errors that can return and all of them seem to be wrapped up differently. I don't know the different variations we can expect; Is there Documentation on smartAPI or the Hubmap API page (Note: Noticed the link to ingest API's github instead links to ingest UI's) that breaks down the different kind of errors we can expect?