Meilisearch — meilisearch rules

# harvested from https://github.com/meilisearch/meilisearch/blob/9d3365c81607e17ec9df1473f97d5dc9109bb1c4/crates/openapi-generator/.spectral.yaml on 2026-10-09 — a Spectral ruleset published in the provider's own GitHub repository (meilisearch/meilisearch); found by GitHub code search, fetched verbatim
x-method: harvested
x-stamped: 2026-10-09
x-source-url: https://github.com/meilisearch/meilisearch/blob/9d3365c81607e17ec9df1473f97d5dc9109bb1c4/crates/openapi-generator/.spectral.yaml
extends: ["spectral:oas"]

rules:
  # Disable the security scopes warning
  # Meilisearch uses Bearer authentication with API key permissions that work like scopes,
  # but OpenAPI 3.0 doesn't support scopes with HTTP Bearer authentication (only OAuth2).
  # The security annotations document required permissions but are not OAuth2 scopes.
  oas3-operation-security-defined: off
  # Some components are generated by utoipa but not referenced in paths (e.g. inlined in generics).
  oas3-unused-component: off
  # Workaround for a nimma (Spectral's JSONPath engine) bug that crashes with
  # "Cannot read properties of null (reading 'enum')" when traversing our spec.
  # The rule's JSONPath ($..[?(@.enum && @.enum.constructor.name === 'Array')])
  # is evaluated against every node including `null` values present in our many
  # response examples (e.g. `"indexUid": null`, `"progress": null`), and nimma
  # does not guard against `@` being null before reading `@.enum`. Since utoipa
  # cannot produce duplicate enum entries from Rust enums anyway, disabling this
  # rule is safe.
  duplicated-entry-in-enum: off