fix(instrumentation-fastify): stop using fastify types in public api

Prior to this commit, the Fastify instrumentation used to expose a few types from the `fastify` lib directly. Exposing these types leads to issues for TypeScript users who depend on the integration but don't depend on `fastify` itself where their TypeScript compilation would fail while complaining that it couldn't find any definitions for `fastify`. This scenario is pretty common when using the auto-instrumentation packages.5 Signed-off-by: Boris Bera <[email protected]>
open-telemetry · Nov 3, 2022 · 863b62c · 863b62c
1 parent ae76570
commit 863b62c
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/plugins/node/opentelemetry-instrumentation-fastify/src/instrumentation.ts b/plugins/node/opentelemetry-instrumentation-fastify/src/instrumentation.ts
@@ -209,7 +209,7 @@ export class FastifyInstrumentation extends InstrumentationBase {
     return fastify;
   }
 
-  public _patchSend() {
+  private _patchSend() {
     const instrumentation = this;
     this._diag.debug('Patching fastify reply.send function');
 
@@ -238,7 +238,7 @@ export class FastifyInstrumentation extends InstrumentationBase {
     };
   }
 
-  public _hookPreHandler() {
+  private _hookPreHandler() {
     const instrumentation = this;
     this._diag.debug('Patching fastify preHandler function');