-
-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix logic for merging object schemas within a property #1159
Open
eli-bl
wants to merge
6
commits into
openapi-generators:main
Choose a base branch
from
eli-bl:issue1123-merge-model
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
850df2e
fix: use correct class name when overriding model property
eli-bl 5cd16ac
misc implementation changes
eli-bl e35b31a
Merge branch 'main' of github.com:openapi-generators/openapi-python-c…
eli-bl e6cdf95
lint
eli-bl c363974
simplify a bit
eli-bl 9e7e7b1
Merge branch 'upstream-main' into issue1123-merge-model
eli-bl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
--- | ||
default: patch | ||
--- | ||
|
||
# Fix overriding of object property class | ||
|
||
Fixed issue #1123, in which a property could end up with the wrong type when combining two object schemas with `allOf`, if the type of the property was itself an object but had a different schema in each. Example: | ||
|
||
```yaml | ||
ModelA: | ||
properties: | ||
status: | ||
type: string | ||
result: | ||
- $ref: "#/components/schemas/BaseResult" | ||
|
||
ModelB: | ||
allOf: | ||
- $ref: "#/components/schemas/ModelA" | ||
- properties: | ||
result: | ||
- $ref: "#/components/schemas/ExtendedResult" | ||
|
||
ModelC: | ||
allOf: | ||
- $ref: "#/components/schemas/ModelA" | ||
- properties: | ||
result: | ||
- $ref: "#/components/schemas/UnrelatedResult" | ||
|
||
BaseResult: | ||
properties: | ||
prop1: | ||
type: string | ||
|
||
ExtendedResult: | ||
allOf: | ||
- $ref: "#/components/schemas/BaseResult" | ||
- properties: | ||
prop2: | ||
type: string | ||
|
||
UnrelatedResult: | ||
properties: | ||
prop3: | ||
type: string | ||
``` | ||
|
||
Previously, in the generated classes for both `ModelB` and `ModelC`, the type of `result` was being incorrectly set to `BaseResult`. | ||
|
||
The new behavior is, when computing `allOf: [A, B]` where `A` and `B` are both objects, any property `P` whose name exists in both schemas will have a schema equivalent to `allOf: [A.P, B.P]`. This is consistent with the basic definition of `allOf`. | ||
|
||
When translating this into Python code, the generator will use a type that correctly describes the combined schema for the property. If the combined schema is exactly equal in shape to either `A.P` or `B.P` (implying that one was already derived from the other using `allOf`) then it will reuse the corresponding Python class. Otherwise it will create a new class, just as it would for an inline schema that used `allOf`. Therefore in the example above, the type of `ModelB.result` is `ExtendedResult`, but the type of `ModelC.result` is a new class called `ModelCResult` that includes all the properties from `BaseResult` and `UnrelatedResult`. |
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need
parent_name
andconfig
now because it might be necessary to generate a new inline schema.