chore(config): consolidate schema metadata application - #25979
Open
pront wants to merge 2 commits into
Open
Conversation
|
pront
force-pushed
the
codex/consolidate-config-metadata
branch
from
July 30, 2026 20:29
40375c7 to
df890e8
Compare
pront
marked this pull request as ready for review
July 31, 2026 18:29
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Consolidates configurable schema metadata application without changing generated schema output.
apply_base_metadatawith the unifiedapply_metadataentry point across generated and handwritten schema codeMetadataMetadata::mergesemantics remain unchanged, and regenerated component documentation has no net diff.Vector configuration
N/A — this refactors schema generation internals and does not change Vector configuration syntax.
How did you test this PR?
On the latest
origin/master:make generate-docsmake check-generated-docscargo test -p vector-configmake check-clippymake check-fmtgit diff origin/master...HEAD --checkChange Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
#14263 — Annotate configurable types to describe their input format
#15001 — Improve generated-doc handling of schema annotations
#16366 — Fix base vs. override schema metadata handling
#15906 — Combine field and type metadata for optional fields