We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some semantic conventions are flagged as deprecated in the model.yaml file, for example net.peer.name.
model.yaml
net.peer.name
When generating C++ code for it, the generated declaration is missing the @deprecated markup.
@deprecated
This is an issue, because code using deprecated semantic conventions goes unnoticed, as it builds without warnings.
It seems the way to represent the deprecated flag has changed in the generator tool.
The code in the opentelemetry-cpp template uses:
{%- if attribute.deprecated %}
while the same in opentelemetry-java was changed recently to
{%- if (attribute.stability | string()) == "StabilityLevel.DEPRECATED" %}
See java PR open-telemetry/opentelemetry-java#4938
The text was updated successfully, but these errors were encountered:
Fix open-telemetry#2275
1b02a62
marcalff
Successfully merging a pull request may close this issue.
Some semantic conventions are flagged as deprecated in the
model.yaml
file, for examplenet.peer.name
.When generating C++ code for it, the generated declaration is missing the
@deprecated
markup.This is an issue, because code using deprecated semantic conventions goes unnoticed, as it builds without warnings.
It seems the way to represent the deprecated flag has changed in the generator tool.
The code in the opentelemetry-cpp template uses:
while the same in opentelemetry-java was changed recently to
See java PR open-telemetry/opentelemetry-java#4938
The text was updated successfully, but these errors were encountered: