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
feature request
My code has a big section of private code, but also a public API. Both are full of jsdoc annotations.
The API part has @preserve annotation (very nice feature!), so my users have jsdoc for intellisense support. It would be nice if we could skip mangling variable names for those API functions, so provide better support in chrome devTools console in runtime:
I had to add about 100 variable names in the array, but it worked.
This approach is not so easy to maintain and has the drawback to not mangle private code.
Thanks for the hint!
feature request
My code has a big section of private code, but also a public API. Both are full of jsdoc annotations.
The API part has
@preserve
annotation (very nice feature!), so my users have jsdoc for intellisense support. It would be nice if we could skip mangling variable names for those API functions, so provide better support in chrome devTools console in runtime:Without mangling we have
ref #3263
The text was updated successfully, but these errors were encountered: