GQL Resolver for ClinicalError needed to be defined in two places, once for direct query from root and then again from nested in clinicalData. This was found because the getClinicalError api funciton was broken in the previous PR, so this was fixed in a way to satisfy both.
In addition, it was found that the clinical API was not parsing the JSON bodies without the Content-Type header set to application/json so that was added to the POST requests.
Description of changes
GQL Resolver for ClinicalError needed to be defined in two places, once for direct query from root and then again from nested in clinicalData. This was found because the getClinicalError api funciton was broken in the previous PR, so this was fixed in a way to satisfy both.
In addition, it was found that the clinical API was not parsing the JSON bodies without the
Content-Typeheader set toapplication/jsonso that was added to the POST requests.Type of Change