← Back to rules

eslint/no-nested-ternary Style

What it does

Disallow nested ternary expressions.

Why is this bad?

Nested ternary expressions make code harder to read and understand. Nesting of these expressions can lead to complex logic that is difficult to understand.

Examples

Examples of incorrect code for this rule:

const result = condition1 ? (condition2 ? "a" : "b") : "c";

Examples of correct code for this rule:

let result;
if (condition1) {
  result = condition2 ? "a" : "b";
} else {
  result = "c";
}

How to use

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

Config (.oxlintrc.json)

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

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

export default defineConfig({
  rules: {
    "no-nested-ternary": "error",
  },
});

CLI

oxlint --deny no-nested-ternary

Version

This rule was added in v0.15.4.

References

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