Each kind of response is slightly different, but this tries to make them more consistent in a few ways:
- No more gene vs normalized gene object. Everything is a GA4GH core
Gene
. This means no moreassociated_with
vsxref
, so one less kind ofMatchType
. - The outermost level includes the query, additional parameters passed to the API endpoint (I think (...?) this is good practice to include) and service information
- The outermost level also includes a
match
key that points to what the individual PythonQueryHandler
methods would return. IMO it makes more sense to move this stuff into the REST API response because these are things that you don't otherwise typically include in Python-to-Python methods (e.g. another class doesn't need to know what version of Gene Normalizer is running, it's literally sharing the environment). match
objects include source metadata and warnings. In some of the responses, we have previously included source metadata closer to the actual source matches, b