API/DAO Metadata - Retain versioning metadata for possible usage in runtime+tooling #17735
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.
Overview
This is an excerpt from #17729. It makes available more metadata to indicate when fields were created.
Before
In
xml/schema/**
, there is information about when fields were created. However, this information is not passed through to the DAOs - so it cannot be presented at runtime.After
The metadata is part of the DAO's
fields()
tree.Comments
I extracted this from #17729 because (a) this part is large and prone to growing stale and (b) there are a few different things going on in the original PR, and it may take a bit longer to sort the functional changes. However, this part seems like very low-hanging fruit.
Additionally, the metadata may have multiple uses (e.g. improving the docs which are built into the API Explorer).