Alphabetize union types for __typename values for codegen

Help
,
1

Hello, my company is using the apollo client codegen tool, and we often use Union types, so we’ve added the flag to add the __typename field to the generated .ts files as outlined in the documentation: Developer tools - Apollo GraphQL Docs . A problem we are encountering is that the fields that are added to the resulting .ts files that are not generated are not idempotent. We run this tool locally, and every person’s machine seems to produce a different ordering for the values listed in the resulting options for the __typename field for the generated types.

It doesn’t affect how it works, it’s fine, but it creates huge diffs. Any idea how to make these fields sorted or otherwise their order idempotent on generation?
Our graphql schema files may looks something like this in a file called foofile.graphql :

type Foo {
   fooThing Fooable
}

interface Fooable {
  name: String!
}

type Bar implements Fooable {
  name: String!
}

type Baz implements Fooable {
  name: String!
}

type Blop implements Fooable {
  name: String!
}

extend type query {
   getFoo(fooID: string!): Foo!
}

We will then write a query in the typescript code to use these types:

export const GET_FOO = gql`
  query getFoo($fooID: string!) {
     name
  }
`

and then run the codegen to generate the needed types. But, on one run of codegen, it may produce a file like:

export interface getFoo_Foo {
  __typename : "Bar" | "Baz" | "Blop"
 name: string
}

And then on another run of codegen, using someone else’s machine with no changes to the source files (the .graphql or the .ts file with the hand-written query), it may produce:

export interface getFoo_Foo {
  __typename : "Blop" | "Baz" | "Bar"
  name: string
}