Add vendor extension support to Content.Encoding type #405
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.
Issue #315
This PR adds vendor extension support to the Content.Encoding type, addressing issue #315. The implementation follows the existing patterns used throughout the codebase for vendor extensions.
Changes made:
The changes are non-breaking as they:
I've implemented these changes in both OpenAPIKit and OpenAPIKit30 to maintain consistency across versions. All tests are passing, including the new vendor extension test cases.
This enhancement allows users to add custom vendor extensions to Content.Encoding objects, following the OpenAPI specification's vendor extension pattern (x-prefixed properties).