[release/9.0] Apply schema transformer to AdditionalProperties#59730
Merged
wtgodbe merged 1 commit intorelease/9.0from Jan 10, 2025
Merged
[release/9.0] Apply schema transformer to AdditionalProperties#59730wtgodbe merged 1 commit intorelease/9.0from
wtgodbe merged 1 commit intorelease/9.0from
Conversation
Contributor
|
Approved via email. |
captainsafia
approved these changes
Jan 10, 2025
This was referenced Feb 12, 2025
1 task
This was referenced Jul 22, 2025
Closed
Closed
Closed
This was referenced Jan 8, 2026
Closed
Closed
This was referenced Jan 17, 2026
Open
This was referenced Jan 30, 2026
Closed
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
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.
Backport of #59699 to release/9.0
/cc @captainsafia @JTeeuwissen
Description
This pull request invokes the schema transformer to the AdditionalProperties field within the JSON schema.
Fixes #59616
Customer Impact
This change is necessary to ensure the schema transformer correctly applies to AdditionalProperties, a sub-field within the JSON schema.
While there are workarounds for this issue, the workarounds require the user to implement an extensive amount of custom code in order to properly recurse into an AdditionalProperties subschemas for a given type.
Regression?
Risk
Low risk because:
Verification
Packaging changes reviewed?