Automatically call out experimental types and properties#359
Merged
jack-berg merged 3 commits intoopen-telemetry:mainfrom Nov 1, 2025
Merged
Automatically call out experimental types and properties#359jack-berg merged 3 commits intoopen-telemetry:mainfrom
jack-berg merged 3 commits intoopen-telemetry:mainfrom
Conversation
…y-configuration into meta-schema-experimental-types
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.
We currently rely on convention to add a warning to a property's description in
meta_schema_types.yamlif it is experimental.This is imprecise and error prone.
In this PR, I automatically flag properties and types as experimental based stability definition:
Experimental/developmentschema-docs.mdcalls out experimental types (example) and properties (example).The descriptive comments added to examples automatically call out experimental properties.