fix(mock): null is excluded instead of being converted to an empty string ''

[soartec-lab]

Status

READY

Description

If null exists in enum, the generated enum type will not include null or the empty string ''.
For example bellow generated by https://github.com/anymaniax/orval/blob/master/tests/specifications/null-type-v3-0.yaml#L91

export type NullableStringEnum = typeof NullableStringEnum[keyof typeof NullableStringEnum] | null;

export const NullableStringEnum = {
  ONE: 'ONE',
  TWO: 'TWO',
  THREE: 'THREE',
} as const;

Therefore, they are unnecessary, including the value patterns generated by mock. In fact, specifying the type causes an error.

export const getFetchNullableEnumsMock = () => (
  faker.helpers.arrayElement([faker.helpers.arrayElement(['ONE','TWO','THREE', ''] as const), null])
)
const mock: NullableStringEnum = getFetchNullableEnumsMock()
// => error TS2322: Type '"" | "ONE" | "TWO" | "THREE" | null' is not assignable to type 'NullableStringEnum'.
//    Type '""' is not assignable to type 'NullableStringEnum'.

So I fixed it so that it doesn't contain the empty string ''''.

export const getFetchNullableEnumsMock = () => (
  faker.helpers.arrayElement([faker.helpers.arrayElement(['ONE','TWO','THREE'] as const), null])
)
const mock: NullableStringEnum = getFetchNullableEnumsMock()
// => not error

Related PRs

none

Todos

• Tests
• Documentation
• Changelog Entry (unreleased)

Steps to Test or Reproduce

1. cd test
2. yarn generate:default
3. Check the getFetchNullableEnumsMock function in tests/generated/default/null-type-v3-0/endpoints.ts