Following #68 we are now auto-generating types for our graphQL queries. However, as seen in #71, the data field in those queries is untyped as it depends on beamline etc. In most cases in the UI we probably know what we expect this type to be though and given we have the schema that these data fields conform to e.g. https://github.com/DiamondLightSource/ulims-json-schemas/blob/main/schemas/experiment_definition/i15-1/room_temperature/0.0.1.json we should be able to autogenerate the full expected type for the query + data.
Acceptance Criteria
- We can autogenerate a full type for returned graphQL queries from the graphQL schema + the ULIMS schema
- How to do this is well documented
- Existing calls to graphQL use this if appropriate
Following #68 we are now auto-generating types for our graphQL queries. However, as seen in #71, the
datafield in those queries is untyped as it depends on beamline etc. In most cases in the UI we probably know what we expect this type to be though and given we have the schema that these data fields conform to e.g. https://github.com/DiamondLightSource/ulims-json-schemas/blob/main/schemas/experiment_definition/i15-1/room_temperature/0.0.1.json we should be able to autogenerate the full expected type for the query + data.Acceptance Criteria