rescript-lang / rescript-lang/rescript-vscode
Build schema is always taken from the compiler's latest master
Nobody has claimed this yet.
- Dominant language
- ReScript
- Stars
- 354
- Forks
- 63
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 1
Description
Only users of the latest version actually get correct autocompletions for their rescript.json, e.g. I now get
"Property pinned-dependencies is not allowed." in a ReScript 11 project.
We should find some way for
https://github.com/rescript-lang/rescript-vscode/blob/master/package.json#L54
to be aware of the version
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 at package.json line 54, where the build schema is referenced, and inspect how the ReScript compiler version relates to the rescript.json schema. Define how version-specific schemas should be selected or exposed. Done means ReScript 11 projects accept properties such as pinned-dependencies while other compiler versions receive the appropriate schema.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100