.pipe fn type overloads no longer support using spread arguments
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 31.7k
- Forks
- 3k
- PR merge metrics
- No merged PRs in 30d
Description
Bug Report
Current Behavior
After #3945, the following is now a type error:
of(1, 2, 3).pipe(...[map((x) => x)]);
error TS2557: Expected at least 0 arguments, but got 0 or more.
Arguably, this is TS error as witnessed by the odd error msg.
Possible Solution
Not sure if it is possible to have the good behaviors #3945 introduced in terms of error reporting and passing spread args.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source file or test; start by reviewing the .pipe overload changes from #3945 and reproduce the TypeScript error with the shown of/map example. Done means spread arguments compile again without regressing the error-reporting behavior introduced there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100