---
title: "unicorn/prefer-logical-operator-over-ternary"
description: "Require `||` or `??` instead of a ternary that repeats its condition"
# Generated by src/codegen/lint-rule-docs.ts. Do not edit below this line.
plugin: "unicorn"
aliases: []
kind: "suggestion"
category: "style"
default: "off"
fixable: "suggestion"
typeAware: false
deprecated: false
---

`user.name ? user.name : "Anonymous"` writes `user.name` twice and evaluates it twice. `user.name || "Anonymous"` gives the same result and evaluates it once.

The rule reports `a ? a : b` and `!a ? b : a`.

{/* Generated by src/codegen/lint-rule-docs.ts. Do not edit this section. */}

## Configure

Off by default. To turn it on:

```toml bunfig.toml
[lint.rules]
"unicorn/prefer-logical-operator-over-ternary" = "error" # or "warn"
```

{/* End of the generated section. */}

## Examples

Reported:

{/* bad {"count": 2} */}
```js
const name = user.name ? user.name : "Anonymous";
const port = !config.port ? 3000 : config.port;
```

Not reported:

{/* good */}
```js
const name = user.name || "Anonymous";
const port = config.port || 3000;
```

If the fallback is only meant for `null` and `undefined`, so that `0` and `""` are kept, use `??`:

{/* good */}
```js
const port = config.port ?? 3000;
```