Paul Draper

Copying from https://github.com/APIDevTools/swagger-parser/issues/127#issuecomment-922634697 --- The obvious -- if annoying -- workaround is to put components first, and reference everything there. Example input **example.yml** ```yml openapi: "3.0.3" components: # reference everything...

> at least anecdotally I've not personally seen a lot of namespace usage in TS circles Except for, you know, TS itself. ;)

> Backends should already be able to deduce the type of action using the attributes added to spans according to the semantic conventions defined in this spec. The easiest way...

> the fact that component is redundant Not really. Without it, you need to add information (an algorithm for deducing type) that you wouldn't otherwise. > This definition would not...

**1. Does anyone use Datadog?** Or am I the only user of the largest commercial monitoring platform? Because I don't see how Otel is going to work with Datadog using...

I agree with @dyladan . (A) The tracer is already managing context (activeSpan, withActiveSpan). (B) Fewer places is better.

`service.name` doesn't imply process-level isolation, just the logical name of a service. > Logical name of the service. MUST be the same for all instances of horizontally scaled services. Is...

Example: ```sh mkdir project echo sbt.version=1.2.3 > project/build.properties echo import example._ > A.scala echo 'class A {}' >> A.scala echo 'class B {}' > B.scala sbt compile # fail echo...

See install command; version is 3.1.0. https://github.com/rollup/plugins/blob/master/packages/pluginutils/package.json (And enhanced-resolve version is 5.8.3.)

Excellent that worked. Thanks for the fast help! I don't know enough to say what is "at fault" but for my case, I am looking to match Node.js `require.resolve` (I'm...