microsoft / microsoft/TypeScript-Sublime-Plugin
Syntax specific settings from `TypeScript.sublime-settings` should override built-in `Preferences.sublime-settings`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 236
- Avg merge
- 21d 13h
- Merged PRs (30d)
- 1
Description
Context:
Sublime Text 3 build 3083, Mac OS X 10.9.5
- Install
TypeScript-Sublime-Pluginvia Package Control or source - Open up a TypeScript file, ensure that TypeScript is the active syntax
- Open
TypeScript.sublime-settingsby navigating the menu barSublime Text->Preferences->Settings - More->Syntax Specific - User - Insert the following:
{ "typescript_auto_format": false } - Restart ST3
- Open TypeScript file, type
var x=1 - Type
;
Expected behavior: I end up with var x=1;
Actual behavior: I end up with var x = 1;
I shouldn't have to touch the package's own Preferences.sublime-settings file. That file gets overwritten on subsequent installs, so it's not a good place for my personal user preferences.
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
Reproduce the behavior using TypeScript.sublime-settings and the package's Preferences.sublime-settings, following the steps in the issue. Then trace how the plugin loads syntax-specific and built-in settings, and verify that a user value for typescript_auto_format takes precedence without editing the package file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100