You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the comment in #1332 -
I have been considering providing an easier way to inject queue items as part of the snippet config, but for now the above would be the approach.
Rather than requiring everyone to directly reference the aiSdk.queue array to add callback methods, provide a callback that is executed once the Sdk is successfully loaded and initialized.
Usage of the aiSdk.queue array is problematic as during initialization the value array is actually deleted (become undefined) and if the sdk has already been loaded and initialized by something else injected on to a hosting page then the reference appInsights instance may not actually be the active sdk instance.
The text was updated successfully, but these errors were encountered:
Tagging as "fixed" waiting release even though strictly speaking the snippet can be used as is from the readme
This is more for release tracking when we go to create the release notes.
As per the comment in #1332 -
I have been considering providing an easier way to inject queue items as part of the snippet config, but for now the above would be the approach.
Rather than requiring everyone to directly reference the aiSdk.queue array to add callback methods, provide a callback that is executed once the Sdk is successfully loaded and initialized.
Usage of the aiSdk.queue array is problematic as during initialization the value array is actually deleted (become undefined) and if the sdk has already been loaded and initialized by something else injected on to a hosting page then the reference appInsights instance may not actually be the active sdk instance.
The text was updated successfully, but these errors were encountered: