[restrict-template-expressions] change option name allowNullable
to allowNullish
#1810
Labels
breaking change
This change will require a new major version to be released
enhancement
New feature or request
package: eslint-plugin
Issues related to @typescript-eslint/eslint-plugin
Milestone
It would make more sense if the option which allows undefined and null would be called "allowNullish" because "nullish" usually refers to a value which is either null or undefined. "nullable type" usually refers to a type which can be
T | undefined | null
.I made this rule and I didn't care about that distinction back then, but I think it is important for consistency. I think it's a good time to change this for 3.0
The text was updated successfully, but these errors were encountered: