Detected the use of variables before they are defined JS-0357
Anti-pattern
Major
a year ago
—
a year old
'renderAlternateLoginMethod' was used before it was defined
69 }
70
71 if (!userInfo.has_webauthn_credential) {
72 return renderAlternateLoginMethod(userInfo.id); 73 }
74
75 userID = userInfo.id;'renderAlternateLoginMethod' was used before it was defined
91 }
92
93 if (e instanceof WebauthnRequestCancelledError) {
94 return renderAlternateLoginMethod(userID); 95 }
96
97 throw e;'renderAlternateLoginMethod' was used before it was defined
106 return renderPasscode(info.id, config.password.enabled, true);
107 }
108
109 return renderAlternateLoginMethod(info.id);110 })
111 .catch((e) => {
112 if (e instanceof NotFoundError) {'passcodeSubmit' was used before it was defined
63 const onPasscodeInput = (digits: string[]) => {
64 // Automatically submit the Passcode when every input contains a digit.
65 if (digits.filter((digit) => digit !== "").length === numberOfDigits) {
66 passcodeSubmit(digits); 67 }
68
69 setPasscodeDigits(digits);
Description
Variables, functions and types should always be used after they've been defined. This issue will flag any code snippets that use variables or types before definition.
Sometimes, the code will run just fine even when the variable is declared after use. Consider the following example:
const ram: Resource = { type: "memory", limit: 1024 ** 3 }
type Resource = {
type: string;
limit: number;
}
Here, Resource is used in the annotation before it has been defined.
Similarly, it is possible to hoist function declarations and variables declared with the var keyword:
const four = twice(2);
function twice(n: number) {
return n * 2;
}
However, it makes the code harder to follow when variables or types are declared after being used.
Bad Practice
const knight: Radiant = {
order: "SurgeBinder"
strength: 30
}
interface Radiant {
order: string;
strength: number;
}
Recommended
interface Radiant {
order: string;
strength: number;
}
const knight: Radiant = {
order: "SurgeBinder"
strength: 30
}