fix(instrumentation-openai)!: add missing access modifiers to private methods #3242
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3240
Introduced via #3164 -> #3157
Errors stem from OpenAI types being used in the instrumentation's public interface. Instrumentations are supposed to no-op without causing errors even if the instrumented package is not installed.
This PR fixes this by adding
privateaccess modifiers theOpenAIInstrumentationintended private properties. This will rease the types in the compile output and removes the imports.You can test this by following these steps:
mainnpm ci && npm run compile./packages/instrumentation-openai/build/src/instrumentation.d.tsopenainpm ci && npm run compile./packages/instrumentation-openai/build/src/instrumentation.d.tsopenaishould be goneBefore this change the compiled output looks like this:
After this change the compiled output will looks like this: