-
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
[BUG] The documentation for enableDebug
is incorrect, it should reference enableDebugExceptions
#2014
Comments
IMO, v3 is a great time to remove it entirely (and put it in the migration notes). |
Yeh, for v3 I'm changing this to only support |
* [BUG] The documentation for enableDebug is incorrect, it should reference enableDebugExceptions #2014 (#2022) * [BUG] SDK LOAD Failure reporting not working #2027 (#2038) * Add a simple interface to enable custom buffer storage solutions #1419 (#2037) This can be used like: ``` const appInsights = new ApplicationInsights({ config: { enableSessionStorageBuffer: true, bufferOverride: { getItem: (logger, key) => localStorage.getItem(key), setItem: (logger, key, value) => localStorage.setItem(key, value), } } }); ``` Co-authored-by: Nev <54870357+MSNev@users.noreply.github.com> * [Master] Add readme documentation for IStorageBuffer (#2045) * [Release] Increase version to 2.8.12 (#2046) --------- Co-authored-by: Philip Peitsch <philip.peitsch@gmail.com>
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
As part of investigating the configuration for #2013 we identified that the documented
enableDebug
flag is not used during the initialization of the SDK and instead is usingenableDebugExceptions
For previous released versions (v2.x) we should update the documentation to point out that this is called
enableDebugExceptions
, and for later releases we shoudl "consider" whether to use theenableDebug
with a fallback toenableDebugExceptions
.As this is really a developer time (non-production) setting, I'm inclined to only support 1 value rather than 2 (from a code size perspective).
The text was updated successfully, but these errors were encountered: