This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Docs/Naming: Standardize on "Promise" or "Thenable" in rule names #5946
Labels
documentation
Documentation ("docs") that needs adding/updating
triage
Waiting for team members to take a look
Before You File a Documentation Request Please Confirm You Have Done The Following...
Suggested Changes
One rule directly refers to Thenables:
@typescript-eslint/await-thenable
Other rules refer to Promises:
@typescript-eslint/no-floating-promises
@typescript-eslint/no-misused-promises
@typescript-eslint/promise-function-async
IMO it's confusing how only one rule refers to Thenables... even though that's technically the correct term.
Thoughts: should we rename some rule(s) for clarity vs. discoverability? I haven't re-looked deeply into the rules, but if no-floating-promises & no-misused-promises actually work on all Thenables (and not just Promises) then maybe we should call them all thenables? Or maybe most users don't know what a Thenable is, and we should always say Promises?
Affected URL(s)
https://typescript-eslint.io/rules/
The text was updated successfully, but these errors were encountered: