fix: Apply required overrides from allOf schemas #1384
Merged
+232
−0
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 an issue where
requiredfield overrides inallOfschemas were being ignored when the base schema was referenced. Properties inherited from a base schema can now be correctly marked as required in derived schemas.Problem
When using
allOfwith a reference to a base schema and then marking fields as required in a second schema, the generator was ignoring the required override. For example:New behavior
A field will be
requiredif it was markedrequiredin the base schema or the derived schema. There is no way to remove arequiredrestriction in a derived schema. This is because for a message to be valid under anallOf, it must be valid under all of the parent schemas.