refactor: use SpecVersion enum in ObjectMapperFactory in preparation for OAS 3.2
ย
MA
2mo ago+95+95+01234567890123456789-71-71-01234567890123456789
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 https://github.com/swagger-api/swagger-core/issues/5181
Type of Change
- ๐ Bug fix
- โจ New feature
- โป๏ธ Refactor (non-breaking change)
- ๐งช Tests
- ๐ Documentation
- ๐งน Chore (build or tooling)
Checklist
- I have added/updated tests as needed
- I have added/updated documentation where applicable
- The PR title is descriptive
- The code builds and passes tests locally
- I have linked related issues (if any)