src/content/docs/linter/rules/no-this-in-static.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="JavaScript (and super languages)" icon="seti:javascript"> ## Summary - Rule available since: `v1.3.1` - Diagnostic Category: [`lint/complexity/noThisInStatic`](/reference/diagnostics#diagnostic-category) - This rule is **recommended**, meaning it is enabled by default. - This rule has a [**safe**](/linter/#safe-fixes) fix. - The default severity of this rule is [**warning**](/reference/diagnostics#warning). - Sources: - Same as [`@mysticatea/no-this-in-static`](https://github.com/mysticatea/eslint-plugin/blob/master/docs/rules/no-this-in-static.md){
"linter": {
"rules": {
"complexity": {
"noThisInStatic": "error"
}
}
}
}
Disallow this and super in static contexts.
In JavaScript, the this keyword in static contexts refers to the class (the constructor) instance,
not an instance of the class. This can be confusing for developers coming from other languages where
this typically refers to an instance of the class, not the class itself.
Similarly, super in static contexts refers to the parent class, not an instance of the class.
This can lead to unexpected behavior if not properly understood.
This rule enforces the use of the class name itself to access static methods,
which can make the code clearer and less prone to errors. It helps to prevent
misunderstandings and bugs that can arise from the unique behavior of this and super in static contexts.
class A {
static CONSTANT = 0;
static foo() {
this.CONSTANT;
}
}
class B extends A {
static bar() {
super.CONSTANT;
}
}
class B extends A {
static ANOTHER_CONSTANT = A.CONSTANT + 1;
static foo() {
A.CONSTANT;
B.ANOTHER_CONSTANT;
}
bar() {
this.property;
}
}
class A {
static foo() {
doSomething()
}
bar() {
A.foo()
}
}