-
Notifications
You must be signed in to change notification settings - Fork 891
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
Make the specification more flexible #175
Comments
+1 |
Thanks for pointing that out! Closing in favor of #165 |
TuckTuckFloof
pushed a commit
to TuckTuckFloof/opentelemetry-specification
that referenced
this issue
Oct 15, 2020
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this issue
Oct 21, 2024
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this issue
Oct 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now a very specific API is enforced that is Java-centric and makes for a very poor API in most languages. The specification should focus more on concepts that should be implemented and not specific classes and methods.
So far, almost every time a change was proposed in
opentelemetry-js
that would make the API a lot better and idiomatic for the user was rejected as it doesn't conform to the spec. This means that we are currently forced to implement an API that makes no sense for JavaScript.The text was updated successfully, but these errors were encountered: