Skip to content
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

Consistently format enums, fix non-identifier IDs. #1863

Merged
merged 5 commits into from
Aug 20, 2021

Conversation

Oberon00
Copy link
Member

Fixes #1519 (again) and also fixes some ids containing spaces (Alibaba Cloud -> alibaba_cloud) or starting with numbers (1xRTT -> csma2000_1xrtt) which tripped up code generators (open-telemetry/build-tools#59).

Changes

Changes enum IDs to be lowercase.

Also changes values and briefs of net.host.connection.subtype and rpc.grpc.status_code to match the IDs. http.flavor is left unchanged since it is already quite old (but http.flavor should probably be refactored anyway separately).

@Oberon00 Oberon00 requested review from a team August 11, 2021 13:02
@Oberon00 Oberon00 added area:semantic-conventions Related to semantic conventions spec:resource Related to the specification/resource directory spec:trace Related to the specification/trace directory labels Aug 11, 2021
@@ -22,6 +22,10 @@ release.

### Semantic Conventions

- BREAKING: Change enum member IDs to lowercase without spaces, not starting with numbers.
Copy link
Member Author

@Oberon00 Oberon00 Aug 11, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a breaking change, but to an experimental part and only in recently added enum members.

@carlosalberto
Copy link
Contributor

@Oberon00 Regarding the breaking portion, is it enough to let Maintainers know next Monday, or should we do something else?

@Oberon00
Copy link
Member Author

Oberon00 commented Aug 16, 2021

I think that would be enough, as actual data breakage is only in stuff that is new and experimental. But probably I'm the wrong person to ask that question to. 😃

@carlosalberto
Copy link
Contributor

@tigrannajaryan maybe you have something to say?

@carlosalberto
Copy link
Contributor

@Oberon00 Please update the CHANGELOG so we can merge ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:semantic-conventions Related to semantic conventions spec:resource Related to the specification/resource directory spec:trace Related to the specification/trace directory
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consistently format semantic convention enums
4 participants