Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Closed
Description
Before You File a Documentation Request Please Confirm You Have Done The Following...
- I have looked for existingopen or closed documentation requests that match my proposal.
- I haveread the FAQ and my problem is not listed.
Suggested Changes
TheTypeOrValueSpecifier
utility is used by a couple a few rules now:
no-floating-promises
:feat(eslint-plugin): [no-floating-promises] add option 'allowForKnownSafePromises' #9186 andfeat(eslint-plugin): [no-floating-promises] add 'allowForKnownSafeCalls' option #9234prefer-readonly-parameter-types
:feat(eslint-plugin): [prefer-readonly-parameter-types] added an optional type allowlist #4436
...and is pending for:
no-unnecessary-type-parameters
:Enhancement: [no-unnecessary-type-parameters] Add an option to treat types as "single-use" #9793restrict-template-expressions
:feat: addallow
option forrestrict-template-expressions
#8556 ->Enhancement: [restrict-template-expressions] More permissive type check #8722
We've been saying constantly that we want shared documentation for this thing.@abrahamguo'shttps://github.com/typescript-eslint/typescript-eslint/pull/8556/files#diff-3af7b11cfbfbd4c66519dff13130df296bdf564fbd1056765f1c79dbed9c2485 is a good start. We'll want to add a true docs page for it with the team's recommendations, including:
- All the things already mentioned in those docs
- To avoid using it as an
allow
option whenever possible (+ why) - That there is a single
string
allowed format, but it's deprecated, and will likely eventually be removed (+ why)
Affected URL(s)
https://typescript-eslint.io/packages/type-utils/type-or-value-specifier, maybe?