src/content/docs/linter/rules/no-useless-rename.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="JavaScript (and super languages)" icon="seti:javascript"> ## Summary - Rule available since: `v1.0.0` - Diagnostic Category: [`lint/complexity/noUselessRename`](/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 [**information**](/reference/diagnostics#information). - Sources: - Same as [`no-useless-rename`](https://eslint.org/docs/latest/rules/no-useless-rename){
"linter": {
"rules": {
"complexity": {
"noUselessRename": "error"
}
}
}
}
Disallow renaming import, export, and destructured assignments to the same name.
ES2015 allows for the renaming of references in import and export statements as well as destructuring assignments. This gives programmers a concise syntax for performing these operations while renaming these references:
import { foo as bar } from "baz";
export { foo as bar };
let { foo: bar } = baz;
With this syntax, it is possible to rename a reference to the same name. This is a completely redundant operation, as this is the same as not renaming at all.
import { foo as foo } from "bar";
export { foo as foo };
let { foo: foo } = bar;
import { foo as bar } from "baz";
export { foo as bar };
let { foo: bar } = baz;