-
Notifications
You must be signed in to change notification settings - Fork 351
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
Only set unset additionalProperties
fields to false
#2310
Conversation
@snoyberg apologies for the delay. It would be great if you could run your codegen against this patch and see if the schemas look good. If they do, we can merge this. |
Thank you @aumetra! I can confirm that with this change, we end up with the correct generated schema files. Much appreciated! |
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
@@ -19,5 +19,6 @@ thiserror = "1.0.26" | |||
|
|||
[dev-dependencies] | |||
anyhow = "1.0.57" | |||
insta = { version = "1.41.1", features = ["json"] } |
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.
Nice, didn't know this one yet.
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.
Yeah, it's pretty neat! Even though it adds a few dev dependencies, but since the PR with the new schema format makes pretty extensive use of insta
there's no damage in introducing it here already
Could you add a changelog entry? |
Oh, looks like we should unify the changelogs of the release branches with main and start a new entry after the 2.2 release. |
Closes #2309