eslint/no-useless-return Pedantic

🚧 An auto-fix is planned for this rule, but not implemented at this time.

What it does

Disallows redundant return statements.

Why is this bad?

A return; statement with nothing after it is redundant, and has no effect on the runtime behavior of a function. This can be confusing, so it's better to disallow these redundant statements.

Examples

Examples of incorrect code for this rule:

function foo() { return; }

function bar() {
    doSomething();
    return;
}

function baz() {
    if (condition) {
        doSomething();
        return;
    }
}

Examples of correct code for this rule:

function foo() { return 5; }

function bar() {
    if (condition) {
        return;
    }
    doSomething();
}

function baz() {
    return doSomething();
}

How to use

To enable this rule using the config file or in the CLI, you can use:

Config (.oxlintrc.json)

{
    "rules": {
        "no-useless-return": "error"
    }
}

CLI

oxlint --deny no-useless-return

References

• Rule Source