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
Follow up to #1647 , where it was pointed out that arrays of primitives should be allowed as the value in KV pairs as per spec.
Describe the solution you'd like:
Our current behavior will throw an exception (post #1647) if invalid data types are used as the values.
Describe alternatives you've considered.
We have an obligation to the spec to support this, right? I'm not sure about the extent to which we currently achieve everything the spec prescribes.
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered:
Current issue in OTel specification: open-telemetry/opentelemetry-specification#1184 Don't want to work on this until this is confirmed.
Sorry, something went wrong.
@Austin-Tan the spec issue is ready to be closed. We can address this now.
Sounds good, feel free to assign this to me. I'll work on this today.
Austin-Tan
Successfully merging a pull request may close this issue.
Feature Request
Follow up to #1647 , where it was pointed out that arrays of primitives should be allowed as the value in KV pairs as per spec.
Describe the solution you'd like:
Our current behavior will throw an exception (post #1647) if invalid data types are used as the values.
Describe alternatives you've considered.
We have an obligation to the spec to support this, right? I'm not sure about the extent to which we currently achieve everything the spec prescribes.
Additional Context
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: