Add instructions for helm-ls to docs

[FichteFoll]

No description provided.

[netlify]

✅ Deploy Preview for sublime-lsp ready!

Name	Link
🔨 Latest commit	8d258c9
🔍 Latest deploy log	https://app.netlify.com/sites/sublime-lsp/deploys/67b4a2646716580008976861
😎 Deploy Preview	https://deploy-preview-2589--sublime-lsp.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[predragnikolic]

Thanks @FichteFoll for the PR.

---

I also want to communicate a mistake on my part.
Wanted to squash and merge the commits, but incidentally selected rebase and merge. (I always forget... I know that some people do not like that :) )

[qvalentin]

Hi @FichteFoll, with version v.0.3.0 helm-ls should now also be enabled for values.yaml files (mrjosh/helm-ls#61 (comment)).
Do you have an idea how this can be configured for sublime?

[FichteFoll]

An LSP expert would need to comment on whether an LSP plugin can be active for files with specific names as I'm currently not aware of a way to do so (and don't have the time to look into it in detail). That does not mean there isn't one, however.

[jwortmann]

The Sublime LSP client identifies the applicable documents based on the syntax scope instead of file patterns. So the best way would probably be to create a small "dummy" syntax that only applies to files with the name values.yaml (assuming this should be the exact filename). For example

%YAML 1.2
---
name: YAML (values.yaml)
scope: source.yaml.values
hidden: true
hidden_file_extensions:
  - values.yaml

contexts:
  main:
    - include: scope:source.yaml
      apply_prototype: true

Then you can add the new base scope to the selector option in the configuration:

"selector": "source.yaml.go, source.yaml.values",