sindresorhus/eslint-plugin-unicorn

`no-nested-ternary` conflicts with `prettier`

Closed

#2,604 opened on Mar 23, 2025

View on GitHubContributor guide
 (1 comment) (6 reactions) (0 assignees)JavaScript (468 forks)user submission
docsgood for beginnerhelp wanted

Repository metrics

Stars
 (5,022 stars)
PR merge metrics
 (Avg merge 1d 16h) (399 merged PRs in 30d)

Description

I started getting ESLintCircularFixesWarning in my ESLint logs after tweaking the config.

I found out it was related to unicorn/no-nested-ternary:

error Nest ternary expression should be parenthesized unicorn/no-nested-ternary

I originally thought it was a conflict with eslint/no-nested-ternary as mentionned in the documentation but while investigating it looks related to prettier:

Delete )eslint(prettier/prettier)

I could not find a way to fix this issue and found another mention os this issue in the Prettier repo which ended up disabling the Unicorn rule:

https://github.com/prettier/eslint-config-prettier/issues/110

Is there a way to fix this conflict? otherwise, should there be a mention about this conflict in the documentation to save troubleshooting time?

Contributor guide

Research direction
Investigate the conflicting rules in eslint plugin unicorn and eslint config prettier. Review linked issue in prettier repo. Determine if a code change is needed to make `no nested ternary` compatible with prettier's formatting, or if the documentation should advise disabling the rule when using prettier. Consider adding a note in the rule's docs about this known conflict.
Tech stack
javascript
Domain
developer experiencetooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
ESLint configurationprettier knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40