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
The bug in question is this line: [tokenHeaderName]: ft. As you can see the tokenHeaderName is passed into the initializePage function and the minifier will change this variable to ut but it will not replace this reference to it on this line.
When unminified, this code is supposed to add a new property to the new JavaScript object where the property name is the string value assigned to the variable. So if tokenHeaderName has the string value of "RequestToken" then the object would have a RequestToken field.
However, instead tokenHeaderName is undefined because the minifier renamed the variable.
Expected behavior
The [tokenHeaderName]: tokenValue syntax in Javascript should also be minified to use the minified variable name.
So in the example given, this should have been minified to output: [ut]: ft
The text was updated successfully, but these errors were encountered:
Describe the bug
The un-minified code looks like the following:
And when minified using
BundlerMinifier
the output is this:The bug in question is this line:
[tokenHeaderName]: ft
. As you can see thetokenHeaderName
is passed into theinitializePage
function and the minifier will change this variable tout
but it will not replace this reference to it on this line.When unminified, this code is supposed to add a new property to the new JavaScript object where the property name is the string value assigned to the variable. So if
tokenHeaderName
has the string value of"RequestToken"
then the object would have aRequestToken
field.However, instead
tokenHeaderName
is undefined because the minifier renamed the variable.Expected behavior
The
[tokenHeaderName]: tokenValue
syntax in Javascript should also be minified to use the minified variable name.So in the example given, this should have been minified to output:
[ut]: ft
The text was updated successfully, but these errors were encountered: