-
Notifications
You must be signed in to change notification settings - Fork 237
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
V3 Beta - Remove Legacy code and ES3 support from V2 SDK #1888
Conversation
MSNev
commented
Aug 18, 2022
- Remove ES3 polyfills (Breaking change from V2)
- Remove Deprecated (v1) API compatibility layer (Breaking change from V2)
- Remove unused namespace globals (Breaking change from V2)
- Document breaking changes
c8f9761
to
fd5bac5
Compare
…n process Task 13988566: [Beta] Remove Legacy code from V2 SDK - Remove Exported namespace globals
fd5bac5
to
ffbf5a4
Compare
@@ -57,7 +54,7 @@ export interface Snippet { | |||
} | |||
|
|||
export interface IApplicationInsights extends IAppInsights, IDependenciesPlugin, IPropertiesPlugin { | |||
appInsights: ApplicationInsights; | |||
appInsights: AnalyticsPlugin; |
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.
I am just curious, ApplicationInsights
includes deprecated instance, so we switch to analyticsplugin
directly here?
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.
For this one I renamed the exported object from "ApplicationInsights" to "AnalyticsPlugin" a few releases ago and as part of this (for backward compatibility) it also exported the "AnalyticsPlugin" as "ApplicationInsights" (so 2 names referencing the same class).