-
Notifications
You must be signed in to change notification settings - Fork 20
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
IFC-592 Merge schemas when loading them from files #5482
base: stable
Are you sure you want to change the base?
Conversation
CodSpeed Performance ReportMerging #5482 will not alter performanceComparing Summary
|
@@ -41,6 +41,7 @@ Jinja2 = "^3" | |||
gitpython = "^3" | |||
pyyaml = "^6" | |||
toml = "^0.10" | |||
dulwich = "^0.21" |
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.
Is this needed? This is a dependency which is supposed to be on the Python SDK.
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.
LGTM, one comment though with this approach if we later want to provide detailed error reports if part os the payload is invalid it seems like it might get harder to indicate where the actual error is. We could of course show it against the combined schema. But we can perhaps cross that bridge when we get there.
When loading multiple schemas files, they used to be imported one by one. With this change, the files are now parsed as schemas and then merged together in order to produce a single schema to load. The merge is performed one by one in the order of the files. This means that the schema coming last will overwrite the previous one if they refer to the same nodes.
c35ce4e
to
5ee44f8
Compare
Fixes #4188
When loading multiple schemas files, they used to be imported one by one. With this change, the files are now parsed as schemas and then merged together in order to produce a single schema to load. The merge is performed one by one in the order of the files. This means that the schema coming last will overwrite the previous one if they refer to the same nodes.