-
Notifications
You must be signed in to change notification settings - Fork 710
Add _NoOpTracer and _NoOpTracerProvider classes #2362
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
Comments
Add `_NoOpTracer` and `_NoOpTracerProvider`. Marking `_DefaultTracer` and `_DefaultTracerProvider` as deprecated. Fixes open-telemetry#2362
Maybe controversial opinion. Do we have to change this? I understand it is not descriptive but these are private classes in api. OTEL makes it clear that in the absence of sdk everything is no-op which I could say default behaviour of the api tracer 🤷. |
@lonewolf3739 |
IMO the implementation/behavior should decide the name of an entity, not where/how it is consumed so noop makes sense to me to over default and since this is internal, changing it should be pretty straightforward while keeping an alias. |
Add `_NoOpTracer` and `_NoOpTracerProvider`. Marking `_DefaultTracer` and `_DefaultTracerProvider` as deprecated. Fixes open-telemetry#2362
* Add _NoOpTracer and _NoOpTracerProvider classes Add `_NoOpTracer` and `_NoOpTracerProvider`. Marking `_DefaultTracer` and `_DefaultTracerProvider` as deprecated. Fixes #2362 * update changelog * update class * fix lint
As per @ocelotl's comment here the name _Default* doesn't make it clear what the behaviour is. This issue suggests creating new classes (_NoOpTracer and _NoOpTracerProvider) and marking _DefaultTracer & _DefaultTracerProvider as deprecated.
The text was updated successfully, but these errors were encountered: