eslint/no-negated-condition Pedantic

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

What it does

Disallow negated conditions.

Why is this bad?

Negated conditions are more difficult to understand. Code can be made more readable by inverting the condition.

Examples

Examples of incorrect code for this rule:

if (!a) {
  doSomethingC();
} else {
  doSomethingB();
}

!a ? doSomethingC() : doSomethingB();

Examples of correct code for this rule:

if (a) {
  doSomethingB();
} else {
  doSomethingC();
}

a ? doSomethingB() : doSomethingC();

How to use

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

Config (.oxlintrc.json)

{
  "rules": {
    "no-negated-condition": "error"
  }
}

CLI

oxlint --deny no-negated-condition

References

• Rule Source