linter: encourage use of NormalCompletion / ReturnCompletion / ThrowCompletion over Completion Records
Open
Nobody has claimed this yet.
linting
- Dominant language
- TypeScript
- Stars
- 245
- Forks
- 80
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 2
Description
Outside of the AOs in question, ecmarkup should warn when it sees a Completion Record { [[Type]]: ~normal~, [[Value]]: ..., [[Target]]: ~empty~ } that could be replaced with NormalCompletion(...). Similarly for ReturnCompletion and ThrowCompletion.
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
Start by locating ecmarkup's linter implementation and how it recognizes Completion Records. Review the related ECMAScript PR for the intended NormalCompletion, ReturnCompletion, and ThrowCompletion forms. Done means the linter warns on the specified equivalent records outside the relevant AOs, with coverage for each replacement form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100