[NOTE] Deprecate language-ids.sublime-settings file

[predragnikolic]

LSP deprecated language-ids.sublime-settings in #2586

This guide is for LSP users who have overridden language-ids.sublime-settings.

Migration guide

1. Opening the command palette and select Preferences: Browse Packages
2. Copy the file from Packages > User > language-ids.sublime-settings and paste the file contents in this issue.
3. Users can delete Packages > User > language-ids.sublime-settings after LSP maintainers added users scopes to the LSP codebase and made a release.

That way the LSP maintainers will add the missing selectors.

LSP will remove language-ids.sublime-settings in the next minor release.

[nicholas-ochoa]

I just noticed this deprecation message and attempted to remove the language-ids.sublime-settings file I had defined, but it ended up causing issues - LSP-TypeScript, LSP-ESLint and LSP-Bash stopped working on my files.

I have a internal/private customized set of syntaxes defined for JavaScript, TypeScript and Bash that embeds Oracle PL/SQL syntax when certain criteria is met - basically a template literal or heredoc with --sql added to the first line. While this is extremely useful to me, I don't suspect this is something that would make sense to upstream into any of the LSP packages that I'm currently using.

Is there an alternative to adding these changes to the LSP package that doesn't involve the language-ids.sublime-settings file? Here is the contents of my language-ids.sublime-settings file:

// SublimeText base scope -> LSP Language ID overrides
{
  "source.tscustom": "typescript",
  "source.jscustom": "javascript",
  "source.bashcustom": "bash",
  "source.json5": "json",
}

[jwortmann]

It should work if you modify the base scope in your customized syntaxes like this:

source.tscustom -> source.ts.custom
source.jscustom -> source.js.custom
source.bashcustom -> source.shell.bash.custom
source.json5 -> source.json.json5

That would also make all kind of tmPreferences files work that are defined for the standard scopes in the default packages, for example comment toggle, indentation rules, etc.

[nicholas-ochoa]

That worked, thank you!

[Mr7F]

{
  "text.git.commit": "git-commit"
}

this is needed to make harper-ls work when writing git commit with sublime, what are we supposed to do?

[jwortmann]

{
  "text.git.commit": "git-commit"
}

this is needed to make harper-ls work when writing git commit with sublime, what are we supposed to do?

I added the correct language ID previously to the included mapping, but by mistake I used source scope instead of text. PR #3020 should fix it (you'll need to wait for the next release to get the fix though).