Compiler: Warn when an operation is called not at the top level
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
This is an antipattern we see all the time, where an operation is nested and must be called like post(...)(state):
get('/some-data', (state) => {
post('some-data, state.data)(state)
})
The compiler should be able to detect nested operation calls like this and log some kind of warning to users. It may even be able to suggest a refactor snippet to show what we mean.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the TypeScript compiler entry point that processes operation calls, then inspect how nested calls are represented and whether existing diagnostics are emitted. Done means the compiler detects the nested pattern and reports a clear warning; the optional refactor suggestion should be treated as a separate scope decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100