[no-promise-reject] Remove this rule - it's not in the scope of this project.

Promises are a type of monad which are definitely a part of functional programming.

The no-promise-reject rule is not only outside the scope of this project but it encourages promise antipatterns.

[RebeccaStevens]

https://github.com/microsoft/TypeScript/issues/39680

[whatisaphone]

Since you asked for feedback, I’ll write a bit.

We use this rule at $DAY_JOB. Generally I prefer using monadic error types (a sum type à la Haskell’s Either or Rust’s Option). There are many benefits to treating errors as ordinary values instead of giving them a special form of control flow. Notably in typescript you cannot annotate the type of a Promise rejection (we have Promise<T>, not Promise<T, E>). Promise.reject is the async equivalent of throw, so imo this rule belongs here just as much as the no-throw rule does.