fix: rename 3_2_0.yaml to expected_3_2_0_upgraded.yaml and add upgrade test #129
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.
Summary
Fixes #128
The
3_2_0.yamltest file was incorrectly named - it contained an OpenAPI 3.1.0 document instead of a 3.2.0 document. This was confusing as the naming convention for other test files (e.g.,3_0_0.yaml,3_1_0.yaml) uses the version number to indicate the source document's OpenAPI version.Changes
Renamed and updated testdata file:
3_2_0.yaml→expected_3_2_0_upgraded.yamlAdded test case to
TestUpgrade_Success:WithUpgradeTargetVersion("3.2.0")optionnullable→typearray,example→examples,exclusiveMinimum/MaximumconversionSchema Transformations Tested
nullable: trueon objecttype: [object, "null"]example: 123examples: [123]exclusiveMinimum: true+minimum: 0exclusiveMinimum: 0exclusiveMaximum: false+maximum: 100maximum: 100anyOf+nullable: true{ type: ["null"] }to anyOfTesting
All upgrade tests pass including the new test case: