Array fields always as any if type specified as array

[hlavavit]

I got this kind of property on my object

        permissions:
          type: 
            - array
          items:
            enum:
              - DEBUG
              - EDIT
            type: string

it end up being generated as

  permissions: any[];

but when i change it to

        permissions:
          type: array
          items:
            enum:
              - DEBUG
              - EDIT
            type: string

it suddenly works and generates as

permissions: ("DEBUG" | "EDIT")[];

Happens with objects as well not just enums.

And it happens with json format as well there it works with "type":"array" and does not with "type":["array"]

Its needed for nullable arrays for example "type":["array","null"] since nullable has been removed with 3.1

[smorimoto]

Found 2 possible duplicate issues:

1. Nullable array with $ref is generated as any[] | null #991
2. [Bug] type: ["null", "object"] with additionalProperties generates object instead of Record<string, string> #1536

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[hlavavit]

Yes its propably duplicate, but this one is the most precise, the other bugs came after and only mention its caused by the type beeing nullable.

Its cause if the type is specified as array, even if its not nullable, meaning array of just one type.