microsoft / microsoft/TypeScript-Sublime-Plugin
set customized `tsdk location` on project level
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 236
- Avg merge
- 21d 13h
- Merged PRs (30d)
- 1
Description
On #433 you've added support for editor global setting for tsdk location,
it's common that a developer will have several projects with different typescript version.
if you set of globally in the editor it might break the plugin for some of the projects.
You can read the tsdk location from the project file cascaded to the global preferences file, and the developer will be able to set different typescript version per project.
It should also support relative path, relative to the project file, so it will be possible to do something like:
./node_modules/typescript/lib/tsserver.js
I know sublimelinter infrastructure supports global and per project settings, you can
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 tracing how the plugin currently reads the global tsdk location and how project files are handled. Check the SublimeLinter infrastructure for its global and per-project settings model, then verify that project settings cascade to global preferences and that relative paths resolve from the project file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100