rescript-lang / rescript-lang/rescript-vscode
Revamp snippets
Open
Nobody has claimed this yet.
- Dominant language
- ReScript
- Stars
- 354
- Forks
- 63
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 1
Description
Move producing snippets into the analysis bin so we can make sure they're only produced where it makes sense.
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 the current snippet-producing code and the analysis bin in the repository. Trace where snippets are generated and determine which analysis contexts should allow them. Done means snippet production is handled by the analysis bin and is limited to contexts where it makes sense; no tests are mentioned in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100