Fix more instances of schema missing metadata #13068
Merged
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.
Which issue does this PR close?
This will not close, but rather just helps with the situation in, #12733.
Rationale for this change
As I was trying to fix other issues, I ran into more instances where Schema metadata could theoretically be dropped. These specific issues don't have reproducers (since I just found them while working on other stuff), but I think they are clearly issues nonetheless.
What changes are included in this PR?
Mostly changing
Schema::new
toSchema::new_with_metadata
andschema_builder.finish()
toschema_builder.finish().with_metadata(...)
Are these changes tested?
Yes, all tests still pass.
Are there any user-facing changes?
No