Latest schema does not autogenerate types

[DominicOram]

When trying to generate types against the schema produced in https://github.com/DiamondLightSource/graph-federation/actions/runs/30467711235/job/90629700962 using the documentation from https://github.com/DiamondLightSource/atlas/tree/main/apps/i15-1#updating-supergraph-schema-types I got an error of:

  ❯ Generate to ./src/graphql/__generated__/
    ✔ Load GraphQL schemas
    ✔ Load GraphQL documents
    ✖ OneOf input field JSONOperator.datetimeOperator cannot have a default value.

      OneOf input field JSONOperator.numericOperator cannot have a default value.

      OneOf input field JSONOperator.stringOperator cannot have a default value.
  ❯ Generate to ./src/
    ✔ Load GraphQL schemas
    ✔ Load GraphQL documents
    ✖ OneOf input field JSONOperator.datetimeOperator cannot have a default value.

      OneOf input field JSONOperator.numericOperator cannot have a default value.

      OneOf input field JSONOperator.stringOperator cannot have a default value.

Copilot tells me that this is indeed correct that OneOf is not allowed default values. The issue can be seen from

graph-federation/schema/samples.graphql

Line 111 in 3895062

input JSONOperator @oneOf {

[EmsArnold]

Looks like this is being caused by the default values assigned to JSONOperator in schema/samples.graphql - @DiamondLightSource/ulims-team

input JSONOperator @oneOf {
  stringOperator: StringOperatorInput = null
  datetimeOperator: DatetimeOperatorInput = null
  numericOperator: NumericOperatorInput = null
}

[DominicOram]

Is it worth adding a check in the CI for the graph that the types can be generated from it? Would be annoying if we caught this after a release

[EmsArnold]

I believe it is on our list of things to do, but we will need to tailor this to the clients people are using. For instance, this is an issue using the apollo client (like I15-1), but a relay client (such as ViSR) does not flag this as an issue.