← Back to rules

eslint/no-setter-return Correctness

✅ This rule is turned on by default.

What it does

Setters cannot return values.

This rule can be disabled for TypeScript code, as the TypeScript compiler enforces this check.

Why is this bad?

While returning a value from a setter does not produce an error, the returned value is being ignored. Therefore, returning a value from a setter is either unnecessary or a possible error, since the returned value cannot be used.

Examples

Examples of incorrect code for this rule:

class URL {
  set origin() {
    return true;
  }
}

How to use

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

Config (.oxlintrc.json)

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

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

export default defineConfig({
  rules: {
    "no-setter-return": "error",
  },
});

CLI

oxlint --deny no-setter-return

Version

This rule was added in v0.0.3.

References

• Rule Source
• Upstream rule docs
• Open rule in Oxc Playground