Missing `array` in `flags.type` document

[ybiquitous]

Hi,

Currently, the flags.type possible values are documented as string, boolean, and number:

meow/index.d.ts

Line 11 in 5975fe6

- `type`: Type of value. (Possible values: `string` `boolean` `number`)

Also on README:

https://github.com/sindresorhus/meow#flags

But the actual values by minimist-options include also array:

export type OptionType = 'string' | 'boolean' | 'number' | 'array';

https://github.com/vadimdemedes/minimist-options/blob/f6d24087f871d6605b6c8d0f9c2b36af18467875/index.d.ts#L3

Do these descriptions about flags.type need to include array?

[sindresorhus]

I think we should just use our own type for this instead, without array. Wanna do a PR?

[ybiquitous]

Wait, do you mean array support will be dropped? I feel array is useful...

[sindresorhus]

It was never supported. I don't like array as it doesn't indicate what the array contains. I think this is a better solution: #111

[ybiquitous]

Oh, the array is originated from minimist-options and an undocumented behavior, isn't it?

I have relied on minimist-options to pass multiple values, so I will need to fix...

I think this is a better solution: #111

Make sense. multiple seems better to me too. 😃

[sindresorhus]

Oh, the array is originated from minimist-options and an undocumented behavior, isn't it?

Yup. I didn't even realize it existed.

[ybiquitous]

I understand, thanks. I want to address this issue to fix the meow types! 👍