-
Notifications
You must be signed in to change notification settings - Fork 240
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
Enum element naming consistency #473
Comments
This was referenced May 11, 2023
@open-telemetry/specs-approvers If we fix this we will break some existing code. We are formally allowed to do that but it is still an annoyance. What do you think, is it worth it? |
tigrannajaryan
added a commit
to tigrannajaryan/opentelemetry-proto
that referenced
this issue
May 15, 2023
Other enum element names in this repo are prefixed by enum name in CAPITAL_CASE. This change makes naming of LogRecordFlags and DataPointFlags elements consistent with the rest of the enums. Resolves open-telemetry#473
tigrannajaryan
added a commit
to tigrannajaryan/opentelemetry-proto
that referenced
this issue
May 15, 2023
Other enum element names in this repo are prefixed by enum name in CAPITAL_CASE. This change makes naming of LogRecordFlags and DataPointFlags elements consistent with the rest of the enums. Resolves open-telemetry#473
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most of the enum element names are prefixed by enum name in CAPITAL_CASE, e.g.:
enum StatusCode -> element STATUS_CODE_OK
We have 2 enums that don't follow this rule: LogRecordFlags and DataPointFlags.
Should we fix this?
Need to resolve this for 1.0.
The text was updated successfully, but these errors were encountered: