unicorn/no-nested-ternary Restriction

🛠️ An auto-fix is available for this rule for some violations.

What it does

This rule disallows deeply nested ternary expressions. Nested ternary expressions that are only one level deep and wrapped in parentheses are allowed.

Why is this bad?

Nesting ternary expressions can make code more difficult to understand.

Examples

Examples of incorrect code for this rule:

const foo = i > 5 ? (i < 100 ? true : false) : true;
const foo = i > 5 ? true : i < 100 ? true : i < 1000 ? true : false;

Examples of correct code for this rule:

const foo = i > 5 ? (i < 100 ? true : false) : true;
const foo = i > 5 ? (i < 100 ? true : false) : i < 100 ? true : false;

How to use

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

CLI

oxlint --deny unicorn/no-nested-ternary

Config (.oxlintrc.json)

{
  "rules": {
    "unicorn/no-nested-ternary": "error"
  }
}

References

• Rule Source