fix: defineComponent() with array props

[antfu]

This continues #150, as it's kinda out-of-date. The type declarations are ported from vue-next.

Before

After

[antfu]

Tests passed on my machine but failed on Github Actions. I guess it's because it uses npm without package-lock.json, which may cause dependencies inconsistency. Hold to see if the error still persists after #347 gets merged.

[antfu]

Passed with ts v3.9.4 but failed with the latest v3.9.5. Let's hold it for a while.

[pikax]

Updated to 3.9.5 on vue-next and no error, do you want me to fix this?

[antfu]

@pikax it's might due to that I have moved the array overload in front of the object one. And yes, it would be great if you can help out :)

[pikax]

Replace PropOptions with:

type DefaultFactory<T> = () => T | null | undefined;

interface PropOptions<T = any> {
  type?: PropType<T> | true | null;
  required?: boolean;
  default?: T | DefaultFactory<T> | null | undefined;
  validator?(value: unknown): boolean;
}

[antfu]

It works. Thanks!

[FloryanFilip]

Can I somehow define my prop as tuple value?
plannerDateRange: { type: Array as PropType<[string, string]>, required: true },
The above produces compilation error: