Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Open
Description
Before You File a Bug Report Please Confirm You Have Done The Following...
- I have tried restarting my IDE and the issue persists.
- I have updated to the latest version of the packages.
- I havesearched for related issues and found none that matched my issue.
- I haveread the FAQ and my problem is not listed.
Playground Link
Repro Code
declareconstmaybe:'a'|'b';declareconstfallback:['c'];declarefunctioncreateValues():string[]|undefined;functioncomputeStrings():string[]{constintermediate=maybe==='a'&&createValues();constvalue=intermediate||fallback;returnvalue;}
ESLint Config
module.exports={"rules":{"@typescript-eslint/prefer-nullish-coalescing":"error"}}
tsconfig
{"compilerOptions": {"strictNullChecks":true }}
Expected Result
intermediate
isfalse | string[] | undefined
and its parent function returnsstring[]
. The||
is the right operator to use to makevalue
astring[]
, not astring[] | false
.
Actual Result
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator. 8:30 - 8:32
Additional Info
Related:#7055,#10356, and probably others, searching gives a lot of false positive results...
#10356 notes that this gets suggested a good amount. I personally was surprised to re-discover that the default behavior of the rule is to report in a way that is sometimes incorrect/unnecessary.
Proposal: I think we should switch the rule to ignorefalse | undefined | (always-truthy)
s by default.
💖