0.2.2

This is a smaller release to get some important bugfixes out to you:

Fixes around completion (list now correctly updates with LSP response)
Support for ad-hoc editing without a project folder in the workspace
Fix blocking issue with the initialise message in RLS
Fix completion broken when complete_all_chars set to False

Shout-out to the contributors to this release: @braver, @golddranks, @deathaxe and @randy3k!

0.2.1

Potentially breaking change

Workspaces with multiple root folders will now only set up a language server for the first folder.

Configuration changes:

Global settings:

• diagnostic_gutter_marker
• only_show_lsp_completions
• resolve_completion_for_snippets

Client (language server) settings (including per-project overrides)

• command now supports ~ and sublime variables like ${project_path}
• enabled
• initializationOptions
• settings

Completions and snippets

The javascript/typescript server will no longer provide snippets with completions. LSP added support to fetch and apply snippets using completionItem/resolve, this behaviour can be enabled with the resolve_completion_for_snippets setting.

Contributions:

@randy3k:

• Improved protocol support (initialised notification, version on didOpen)
• Completions fixes (enable sublime's built-in completions, hide details if not available)
• Support for box diagnostics highlighting style.

@rwols:

• Completions: fixed use of insertText when provided.

@rmccue:

• Improved multi-folder workspace handling
• Huge improvement in diagnostics panel updates (to stop flickering)

@chenglou:

• Tested and added configuration for OCaml and Reason

@gmichokostas:

• Tested and added configuration for Go

@braver:

• Fixed LSP status text formatting
• Much solid advice on improving the user experience

@ehuss:

• Fixed a bug preventing Code Actions from being enabled

0.2.0

With this release, LSP's default use of logging and phantoms has been largely disabled.

Word completions and manual completions are now enabled. (#47)
Set complete_all_chars to false to only complete on your language server's trigger chars.

Completions starting with $ (PHP, angular?) are now properly escaped.

Highlighting of diagnostics only visible if SublimeLinter was installed (#26)
LSP now prefers new markup.error scopes in color schemes, but falls back on sublimelinter.mark.error and finally markup.deleted

Language server starts up immediately when start sublime with documents option (#18)

Documentation has been updated with these settings and more client configurations.

Contributions:

@philippotto: handle incompatibility with Flow

@rwols:

• improve highlighting in diagnostics panel
• code improvements

@deathaxe:

• improve highlighting of diagnostics and in references panel
• "No description available" shown when no hover result given.
• code improvements

0.1.0

Initial release after applying some early feedback.

Contributions:

• @rwols added default configuration for clangd
• @frou fixed detection of documents using the built-in javascript syntax