You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello 👋. I came across this project, as I work on a tracer implementation.
The problem
Because of the naming convention opentracing-swift enforces, I'll have to prefix all constructs in my implementation with a custom string, e.g. DDTracer or namespace things by explicitly pointing to the package:
publicclassTracer:OpenTracing.Tracer{
// ...
}
The latter however, might be inconvenient and misleading for users when they import both my implementation and OpenTracing.
Proposed solution
IMHO we might introduce OT prefix in opentracing-swift:
Hello 👋. I came across this project, as I work on a tracer implementation.
The problem
Because of the naming convention
opentracing-swift
enforces, I'll have to prefix all constructs in my implementation with a custom string, e.g.DDTracer
or namespace things by explicitly pointing to the package:The latter however, might be inconvenient and misleading for users when they import both my implementation and
OpenTracing
.Proposed solution
IMHO we might introduce
OT
prefix inopentracing-swift
:OTTracer
,OTSpan
,OTReference
,OTGlobal
,Similar way to what
opentracing-objc
does.This will:
Reference
orGlobal
that they may already use in their projects.I'm curious what's your take on this 🙂?
The text was updated successfully, but these errors were encountered: