-
Notifications
You must be signed in to change notification settings - Fork 55
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
Clean up docs, add syntax.md and semconv.schema.json #53
Clean up docs, add syntax.md and semconv.schema.json #53
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@@ -0,0 +1,235 @@ | |||
# Semantic Convention YAML Language |
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.
As stated in the PR description, this file is copied from https://github.com/open-telemetry/opentelemetry-specification/blob/main/semantic_conventions/syntax.md so that we can have any changes that affect the input format of the semantic convention generator in one PR in one repo, instead of split over spec and build-tools.
Co-authored-by: Armin Ruech <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]>
Very useful for example for auto-completion in VS Code. Co-authored-by: Giovanni Liva <[email protected]> Co-authored-by: Christian Neumüller <[email protected]> Co-authored-by: Gernot Reisinger <[email protected]>
Co-authored-by: Armin Ruech <[email protected]>
Co-authored-by: Armin Ruech <[email protected]>
@open-telemetry/specs-approvers Please review if this seems to be the right direction to go (see PR description). |
As a follow-up I recommend removing the copy of
syntax.md
from https://github.com/open-telemetry/opentelemetry-specification/blob/main/semantic_conventions/syntax.md and adapt the link in https://github.com/open-telemetry/opentelemetry-specification/blob/main/semantic_conventions/README.md.Logically, I think syntax.md needs to be here in the build-tools repository so we can update it in the same PR where we update something about the tool's input parsing (e.g. when adding new features).