Christof Leuenberger

@engelgabriel is this now available?

In this case yes. But another example would be if I wanted to offer additional SpanOptions: opentracing Tracer: ``` startSpan(name: string, options?: SpanOptions): Span; ``` custom Tracer: ``` interface ISpanOptions...

[Here you go](https://github.com/chlab/opentracing-interfaces-demo) Does that help?

Sorry, you're right of course. In eagerness to demonstrate my problem I didn't take time to read the error message properly. I updated my example again though. I'm probably just...

@yurishkuro > there are many tracers that implement this API by extending the base classes (data dog, Jaeger, Lightstep,etc) But for the jaeger node client, you guys aren't extending the...

> The SpanContext is usually where you would put all vendor-specific public properties/methods Probably not all vendor specific properties, only the things you want to propagate from system to system....

To add to this, if you `rm -rf node_modules/*`, then try to `yarn install` again, it says **success Already up-to-date**. If you run `yarn check` it notices all the missing...

I would be willing to help here if someone could tell me where to get started. I have contributed to the documentation [before](https://github.com/backstage/backstage/pull/21788).

@dwelsch-esi thanks for the hint, I was able to setup the docs locally. So what I understand is, that a big part of the audit finding is in the direction...

May I ask what the status is of this branch?