Skip to content

feat: add const keyword validation to built-in validator#1123

Closed
reuvenharrison wants to merge 15 commits intogetkin:masterfrom
oasdiff:fix/builtin-validator-const-keyword
Closed

feat: add const keyword validation to built-in validator#1123
reuvenharrison wants to merge 15 commits intogetkin:masterfrom
oasdiff:fix/builtin-validator-const-keyword

Conversation

@reuvenharrison
Copy link
Contributor

Summary

  • The built-in validator did not enforce the JSON Schema const keyword — schemas with only const set were treated as empty, allowing any value to pass validation
  • Added visitConstOperation method that rejects values not matching the const value, supporting strings, numbers, booleans, objects, and arrays via reflect.DeepEqual
  • Updated IsEmpty() to return false when schema.Const != nil, ensuring const-only schemas are properly validated

Test plan

  • Added TestSchemaConst_BuiltInValidator with 7 sub-tests covering string, number, boolean, null, object, type+const, and multiError scenarios
  • Full test suite passes (go test ./...)

🤖 Generated with Claude Code

Chance Kirsch and others added 15 commits October 2, 2025 08:46
The implementation provides complete OpenAPI 3.1 specification compliance while maintaining 100% backward compatibility with OpenAPI 3.0.

## What Was Implemented

### 1. Schema Object Extensions (openapi3/schema.go)

Added full JSON Schema 2020-12 support with new fields:

- **`Const`** - Constant value validation
- **`Examples`** - Array of examples (replaces singular `example`)
- **`PrefixItems`** - Tuple validation for arrays
- **`Contains`, `MinContains`, `MaxContains`** - Array containment validation
- **`PatternProperties`** - Pattern-based property matching
- **`DependentSchemas`** - Conditional schema dependencies
- **`PropertyNames`** - Property name validation
- **`UnevaluatedItems`, `UnevaluatedProperties`** - Unevaluated keyword support
- **Type arrays** - Support for `["string", "null"]` notation

### 2. Document-Level Features (openapi3/openapi3.go)

- **`Webhooks`** - New field for defining webhook callbacks (OpenAPI 3.1)
- **`JSONSchemaDialect`** - Specifies default JSON Schema dialect
- **Version detection methods**:
  - `IsOpenAPI3_0()` - Returns true for 3.0.x documents
  - `IsOpenAPI3_1()` - Returns true for 3.1.x documents
  - `Version()` - Returns major.minor version string

### 3. License Object (openapi3/license.go)

- **`Identifier`** - SPDX license expression (alternative to URL)

### 4. Info Object (openapi3/info.go)

- **`Summary`** - Short summary of the API (OpenAPI 3.1)

### 5. Types Helper Methods (openapi3/schema.go)

New methods for working with type arrays:

- `IncludesNull()` - Checks if null type is included
- `IsMultiple()` - Detects type arrays (OpenAPI 3.1 feature)
- `IsSingle()` - Checks for single type
- `IsEmpty()` - Checks for unspecified types

### 6. JSON Schema 2020-12 Validator (openapi3/schema_jsonschema_validator.go)

A new opt-in validator using [santhosh-tekuri/jsonschema/v6](https://github.com/santhosh-tekuri/jsonschema):

- Full JSON Schema Draft 2020-12 compliance
- Automatic OpenAPI → JSON Schema transformation
- Converts OpenAPI 3.0 `nullable` to type arrays
- Handles `exclusiveMinimum`/`exclusiveMaximum` conversion
- Comprehensive error formatting
- Fallback to built-in validator on compilation errors
…d formatting and correcting the version logic
The ResolveRefsIn function was not resolving $ref references inside
webhooks, causing Schema.Value to be nil when a webhook operation
referenced a component schema.

This adds webhook ref resolution after the paths loop, using the same
resolvePathItemRef function since webhooks contain PathItem objects.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
In OpenAPI 3.0 (JSON Schema draft-04), exclusiveMinimum/exclusiveMaximum
are booleans that modify minimum/maximum values.

In OpenAPI 3.1 (JSON Schema 2020-12), they are numbers representing
the actual exclusive bounds.

This change introduces ExclusiveBound type that can hold either:
- Bool: for OpenAPI 3.0 style boolean modifier
- Value: for OpenAPI 3.1 style numeric bound

The validation and marshaling logic handles both formats correctly.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The built-in validator did not enforce the JSON Schema const keyword,
allowing any value to pass when only const was set. This adds
visitConstOperation to reject values that don't match the const value,
and updates IsEmpty() to treat schemas with const set as non-empty.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@reuvenharrison
Copy link
Contributor Author

Superseded by #1125 which consolidates all OpenAPI 3.1 PRs into a single PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants