Skip to content

fix: read the OAS 3.1 type back for every schema subclass - #3344

Merged
bnasslahsen merged 1 commit into
mainfrom
fix/3314-schema-type-deserializer
Sep 6, 2026
Merged

fix: read the OAS 3.1 type back for every schema subclass#3344
bnasslahsen merged 1 commit into
mainfrom
fix/3314-schema-type-deserializer

Conversation

@bnasslahsen

Copy link
Copy Markdown
Collaborator

The type deserializer was only registered for JsonSchema, so cloning any other schema subclass still failed and logged a Json Processing Exception warning for every constrained parameter.

Extend the swagger-core mixin so that it can be registered on Schema itself without dropping the serialization it declares, register it on the standalone mappers too, and carry the deserializer over to the sorting mixin that replaces it.

Follow-up to #3315.

Fixes #3314

The type deserializer was only registered for JsonSchema, so cloning any
other schema subclass still failed and logged a Json Processing Exception
warning for every constrained parameter. Extend the swagger-core mixin so
that it can be registered on Schema itself without dropping the
serialization it declares, register it on the standalone mappers too, and
carry the deserializer over to the sorting mixin that replaces it.

Fixes #3314

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@bnasslahsen
bnasslahsen merged commit 90ec2f6 into main Sep 6, 2026
1 check passed
@bnasslahsen
bnasslahsen deleted the fix/3314-schema-type-deserializer branch September 6, 2026 09:24
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.

SpringDocUtils logs Json Processing Exception occurred warning for every @Min-constrained Integer query parameter (regression since 3.1.0)

1 participant