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
May also apply to other deprecation warnings. The current behavior of the deprecation module is to never print out the stack trace, unless it is specifically asked by giving a truthy third parameter to deprecate's deprecationWarning(...). Also, it limits the stack trace to 2 if you simply give it true as the third parameter. 2 lines of stack trace is not useful, considering the first line will be the call to deprecationWarning() and the second will point out the file in which deprecationWarning() is called. E.g. 2 lines of stack trace on a "montage/core/bindings" warning would only point me to montage/core/bindings.js because that is where the deprecationWarning call is.
The text was updated successfully, but these errors were encountered:
May also apply to other deprecation warnings. The current behavior of the deprecation module is to never print out the stack trace, unless it is specifically asked by giving a truthy third parameter to deprecate's deprecationWarning(...). Also, it limits the stack trace to 2 if you simply give it true as the third parameter. 2 lines of stack trace is not useful, considering the first line will be the call to deprecationWarning() and the second will point out the file in which deprecationWarning() is called. E.g. 2 lines of stack trace on a "montage/core/bindings" warning would only point me to montage/core/bindings.js because that is where the deprecationWarning call is.
The text was updated successfully, but these errors were encountered: