anyOf/oneOf incorrectly assume type: object

[MartinKolarik]

resolvers:
  type: array
  items:
    oneOf:
      - type: string
        format: ipv4
      - type: string
        const: private

Renders incorrectly as an array of objects instead of an array of strings:

Similarly, a more basic example without using format:

resolvers:
  type: array
  description: A list of default DNS resolvers configured on the probe.
  items:
    oneOf:
      - type: string
      - type: integer

Should be an array of string | integer but is an array of objects:

[MartinKolarik]

Btw in the first case, I'm also wondering if it wouldn't be better to render both type and format, e.g., string (ipv4) and string (const) or similar.