Skip to content
This repository was archived by the owner on Aug 11, 2025. It is now read-only.
This repository was archived by the owner on Aug 11, 2025. It is now read-only.

Introduce OT prefix #10

@ncreated

Description

@ncreated

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:

public class Tracer: 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:

  • OTTracer,
  • OTSpan,
  • OTReference,
  • OTGlobal,
  • ... .

Similar way to what opentracing-objc does.

This will:

  • minimise the number of prefixes that tracer users have to play with,
  • increase the OT APIs discoverability for tracer developers,
  • let people avoid conflicts with the generic names like Reference or Global that they may already use in their projects.

I'm curious what's your take on this 🙂?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions