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
There is some code in URI.js, that generates warnings in both jsHint and Closure Compiler.
It happens in lines 1646 and 1651:
for (i = 0, p; p = properties[i]; i++) {
CC complains: "WARNING - Suspicious code. This code lacks side-effects. Is there a bug". Since you defined "p" beforehand, you could ommit this declaration in the loop.
Furthermore, jsHint says: "Expected a conditional expression and instead saw an assignment.", because it does not "get" your loop construction, which works, but also can be deemed as a little "funky".
Would be nice if these warnings could be prevented, there shouldn't be much changes needed for that.
The text was updated successfully, but these errors were encountered:
There is some code in URI.js, that generates warnings in both jsHint and Closure Compiler.
It happens in lines 1646 and 1651:
for (i = 0, p; p = properties[i]; i++) {
CC complains: "WARNING - Suspicious code. This code lacks side-effects. Is there a bug". Since you defined "p" beforehand, you could ommit this declaration in the loop.
Furthermore, jsHint says: "Expected a conditional expression and instead saw an assignment.", because it does not "get" your loop construction, which works, but also can be deemed as a little "funky".
Would be nice if these warnings could be prevented, there shouldn't be much changes needed for that.
The text was updated successfully, but these errors were encountered: