Found the usage of undeclared variables JS-0125
Bug risk
3 months ago
—
3 months old
'cy' is not defined
671 .contains("Frontend test data");
672
673 // Save
674 cy.get(675 "div.modal-dialog.modal-xl.modal-dialog-scrollable.modal-dialog-centered.modal-sm"
676 )
677 .children("div")'cy' is not defined
478 .contains("Frontend test model");
479
480 // Save
481 cy.get(482 "div.modal-dialog.modal-xl.modal-dialog-scrollable.modal-dialog-centered.modal-sm"
483 )
484 .children("div")'cy' is not defined
956 .last();
957
958 // Delete newly created user
959 cy.get("#__next >")960 .children("div")
961 .get("table")
962 .children("tbody")'cy' is not defined
947 .last();
948
949 // Check stop solvers button
950 cy.get("#__next")951 .children("div")
952 .children("table")
953 .children("tbody")'cy' is not defined
937 cy.get("#max_cpu").last();
938
939 // Check promote user button
940 cy.get("#__next")941 .children("div")
942 .children("table")
943 .children("tbody")
Description
Variables that aren't defined, but accessed may throw reference errors at runtime.
Potential ReferenceErrors may result from misspellings of variable and parameter names, or accidental implicit globals (for example, forgetting the var keyword in a for loop initializer).
Any reference to an undeclared variable causes a warning, unless the variable is explicitly mentioned in a /*global ...*/ comment, or specified in the globals key in the configuration file.
A common use case for these is if you intentionally use globals that are defined elsewhere (e.g. in a script sourced from HTML).
Bad Practice
const foo = someFunction();
const bar = a + 1; // 'a' is undeclared
Recommended
/*global someFunction, a*/
/*eslint no-undef: "error"*/
const foo = someFunction();
const bar = a + 1;