refactor: use SpecVersion enum in ObjectMapperFactory in preparation for OAS 3.2 - #5255
Open
Mattias-Sehlstedt wants to merge 1 commit into
Conversation
Mattias-Sehlstedt
force-pushed
the
use-spec-version-enum-in-object-mapper-factory
branch
from
July 28, 2026 17:26
869c7d1 to
f7f1f0f
Compare
Mattias-Sehlstedt
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Thank you for contributing to swagger-core!
Please fill out the following information to help us review your PR efficiently.
Description
The swagger ecosystem has started moving towards supporting OAS 3.2. As part of enabling that in swagger-core, it would be helpful to move away from the previous binary openapi31 boolean configuration, and instead attempting to move to using the SpecVersion enum (which can then be extended with V32 and any version that comes after that).
I am unsure of to what extent the project considers all public methods part of the overall contract, and what the removal process is. Thus I have for now deprecated them and pointed towards the replacement.
Relates to #5181
Type of Change
Checklist
Screenshots / Additional Context