-
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
Add Performance / Testing support #1335
Comments
MSNev
pushed a commit
that referenced
this issue
Aug 5, 2020
[BUG] DebugPlugin various updates #1333
MSNev
pushed a commit
that referenced
this issue
Aug 5, 2020
[BUG] DebugPlugin various updates #1333
MSNev
pushed a commit
that referenced
this issue
Aug 5, 2020
[BUG] DebugPlugin various updates #1333
MSNev
pushed a commit
that referenced
this issue
Aug 5, 2020
[BUG] DebugPlugin various updates #1333
MSNev
added
fixed - waiting release
PR Committed and waiting deployment
and removed
fixed - waiting release
PR Committed and waiting deployment
labels
Aug 6, 2020
Fully Deployed to CDN and NPM as version 2.5.7 |
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As part of the changes for #1076, this hides the previously exposed "private" properties and methods on the JavaScript object. So while TypeScript complains we have several customers that consume library directly via JavaScript and they would directly hook / mock these methods for testing / monitoring.
To unblock these users we need to provide a standard method to allow hooking of these methods even for minified code, as the minification process renames these internal non-exposed values (by design to support minifaction)
The text was updated successfully, but these errors were encountered: