-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: splitting BasePlugin into browser and node #981
Conversation
… from node in browser
Codecov Report
@@ Coverage Diff @@
## master #981 +/- ##
==========================================
- Coverage 94.95% 94.90% -0.06%
==========================================
Files 210 211 +1
Lines 8571 8576 +5
Branches 772 772
==========================================
Hits 8139 8139
- Misses 432 437 +5
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are conflicts that need to be resolved but this lgtm
@@ -10,7 +10,7 @@ | |||
"types": "build/src/index.d.ts", | |||
"repository": "open-telemetry/opentelemetry-js", | |||
"scripts": { | |||
"test": "nyc ts-mocha -p tsconfig.json test/**/*.test.ts", | |||
"test": "nyc ts-mocha -p tsconfig.json test/**/*.test.ts --exclude 'test/platform/browser/**/*.ts'", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious to know, why do we have to do this? Also, do you think we should add this to other common packages like api, tracing etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if there are only dedicated tests for browser then this is the way to avoid testing them in mocha. Some of our packages already have things like this, for example collector has common tests and then separate for node and browser.
…n-telemetry#981) * feat: add new instrumentations into auto-instrumentations-node * test: test to make sure all installed instrumentations are added * fix: register the added instrumentations * test: remove the redundant test * fix: add fs instrumentation back I missed during conflict resolution * fix: add config argument to RouterInstrumentation * style: lint it
Which problem is this PR solving?
Short description of the changes