Can enumType.members allow readonly string[]?

[MatthewHerbst]

I have the following data setup (not declaring as an enum because this is shared between TypeScript server code and non-TypeScript client code):

import { enumType } from 'nexus';

export const TYPE_ENUM = Object.freeze({
  H: 'H',
  S: 'S',
});
export const TYPES = Object.freeze(Object.values(TYPE_ENUM));

export const MyType = enumType({
  name: 'MyType',
  members: TYPES,
});

TypeScript is rightly giving me an error here because I'm trying to put TYPES (a readonly string[]) into members which accepts a string[].

https://github.com/graphql-nexus/schema/blob/bf0df64ebd9810f9a458aceb8c5ff52518607825/src/definitions/enumType.ts#L41-L45

To overcome the type issue the best solution I have found so far is to unwrap and then re-create the array: members: [...TYPES]

Is there a better way to overcome the type issue? If not, could enumType.members be modified to allow readonly arrays, or does members need to be mutable?

[radoslavkarlik]

Any update on this? It seems to be an issue with all array types I have encountered.

[jasonkuhrt]

Trying to think if there is any downside to marking the Nexus API as readonly here. I don't think so as that would only widen the accepted set of types.

[jasonkuhrt]

@tgriesser WDTY? I'm sold.

[tgriesser]

Yeah I think that sounds like a fine change. I wish there was a builtin utility type to express Array<T> | ReadonlyArray<T>.