Skip to content

feat: instrumentation scope stable feature parity#2037

Draft
robertlaurin wants to merge 1 commit intomainfrom
feat-stable-instrumentation-scope
Draft

feat: instrumentation scope stable feature parity#2037
robertlaurin wants to merge 1 commit intomainfrom
feat-stable-instrumentation-scope

Conversation

@robertlaurin
Copy link
Contributor

No description provided.

module Trace
# {Tracer} is the SDK implementation of {OpenTelemetry::Trace::Tracer}.
class Tracer < OpenTelemetry::Trace::Tracer
# @api private
Copy link
Contributor

Choose a reason for hiding this comment

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

We have this. Does this give us confidence that we're not going to break anyone by inserting two new params into the param list (before the end)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure we can safely assume no one consuming this package is consuming this private api directly. However with other libraries that assumption is that if you choose to consume a private API you cannot assume it doesn't experience "breaking" changes.

# Returns a new {Tracer} instance.
#
# @param [String] name Instrumentation package name
# @param [String] version Instrumentation package version
Copy link
Contributor

Choose a reason for hiding this comment

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

should document the new params here.

#
# @return [Tracer]
def initialize(name, version, tracer_provider)
def initialize(name, version, schema_url, attributes, tracer_provider)
Copy link
Contributor

Choose a reason for hiding this comment

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

we're not yet storing the new params anywhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants