validate

const (
	// MultipleOfNotPositiveID: JSON Schema validation, "multipleOf" MUST be a
	// number strictly greater than 0.
	MultipleOfNotPositiveID = "multiple-of-not-positive"
	// SubschemasEmptyID: allOf / anyOf / oneOf MUST be a non-empty array.
	SubschemasEmptyID = "subschemas-empty"

	// The remaining rules describe unsatisfiable bounds: min above max means no
	// instance can validate.
	MinimumExceedsMaximumID         = "minimum-exceeds-maximum"
	MinLengthExceedsMaxLengthID     = "min-length-exceeds-max-length"
	MinItemsExceedsMaxItemsID       = "min-items-exceeds-max-items"
	MinPropertiesExceedsMaxPropsID  = "min-properties-exceeds-max-properties"
	MinContainsExceedsMaxContainsID = "min-contains-exceeds-max-contains"
	// EnumEmptyID: JSON Schema says an "enum" array SHOULD have at least one
	// element; an empty one accepts nothing.
	EnumEmptyID = "enum-empty"
	// ConstNotInEnumID: "const" and "enum" together restrict to their
	// intersection, so a const outside the enum accepts nothing.
	ConstNotInEnumID = "const-not-in-enum"
)

Schema-constraint coherence lints: a single schema whose own keywords contradict each other or violate a JSON Schema MUST. The parser accepts all of these (they are well-formed), but no instance can ever satisfy them, so they are authoring mistakes rather than choices. See oasdiff/oasdiff#927.

Severity follows the spec text. A literal MUST violation is an error; a combination the spec does not forbid outright but that no value can satisfy (or a SHOULD) is a warning.

const AmbiguousParameterSerializationID = "ambiguous-parameter-serialization"

AmbiguousParameterSerializationID flags a parameter whose schema type union mixes a structured type (array or object) with a scalar. Style serialization is defined per type and arrays/objects serialize differently from scalars, so for `type: [array, integer]` a server cannot tell whether ?token=5 is the array ["5"] or the integer 5. Valid JSON Schema, under-specified for OpenAPI serialization: an oasdiff-native SHOULD-level lint. See oasdiff/oasdiff#1055.

const DuplicateEnumValueID = "duplicate-enum-value"

DuplicateEnumValueID flags an enum array that contains the same value more than once. JSON Schema says enum elements SHOULD be unique (a recommendation, not a MUST), so kin-openapi does not reject them; this is an oasdiff-native SHOULD-level lint. See oasdiff/oasdiff#980.

const RequiredWithDefaultID = "required-with-default"

RequiredWithDefaultID flags a required parameter or property that also declares a default value. The two contradict each other: `required` means the value must always be present, so the `default` (the value assumed when it is absent) can never apply. It is dead and misleading, and usually a mistake, the author meant the field to be optional. Valid OpenAPI, an oasdiff-native SHOULD-level lint.

const TypeFormatMismatchID = "type-format-mismatch"

TypeFormatMismatchID flags a schema whose `format` is a known format defined for a different `type`, e.g. {"type": "integer", "format": "date-time"}. The format never applies to that instance type, so spec-compliant tooling silently ignores it: not a spec violation, almost always an authoring slip where the type or the format was changed without the other. See oasdiff/oasdiff#1019.