-
Notifications
You must be signed in to change notification settings - Fork 76
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
fix(workspace): update the logging guard to handle ConnectionString for Application Insights #13792
Conversation
…ontend + added unit-tests for it
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #13792 +/- ##
=======================================
Coverage 94.57% 94.57%
=======================================
Files 1623 1624 +1
Lines 21798 21817 +19
Branches 2570 2572 +2
=======================================
+ Hits 20616 20634 +18
- Misses 939 940 +1
Partials 243 243 ☔ View full report in Codecov by Sentry. |
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.
:D
Tested ok, browser errors are once again being logged in AI. |
Description
This pull request addresses an issue with the logging guard in our application. The guard previously checked for the presence of the
instrumentationKey
, but we recently switched to using aconnectionString
without updating the guard logic. As a result, the guard always evaluated as true for the absence ofinstrumentationKey
, which led to Application Insights instances never being created.Related Issue(s)
Verification