Changes in v3.0.0

Released Jul 3, 2020.

JS asset

JVM asset

This is a mayor version with breaking Changes.

This version comes with new LSP 3.15, adopt AMF 4.1.3 and a new set of "EyeCandy" actions.

Breaking changes:

• Move from language server protocol version 3.14 to 3.15.
• JVM: move from lsp4j 0.7.2 to lsp4j 0.9: https://github.com/eclipse/lsp4j/releases/tag/v0.9.0
• JS: move from "vscode-languageserver-protocol" 3.14.1 to 3.15.3 and "vscode-jsonrpc" 4.0.0 to 5.0.1
• Parameters for the following requests have been changed from TextDocumentPositionParams:
  textDocument/declaration changed to DeclarationParams
  textDocument/definition changed to DefinitionParams
  textDocument/typeDefinition changed to TypeDefinitionParams
  textDocument/implementation changed to ImplementationParams
• JVM: The LSP's Protocol Diagnostic field code was previouslyt incorrectly declared as String, it is now correctly declared as Either<String, Number>
• Telemetry: MessageTypes field changed from Integer to string.

Features

EyeCandy:

• ALS-993 - Implement Hover action
• ALS-998 - Implement find file usage
• ALS-999 - Implement document highlight
• ALS-1000 - Implement renaming
• ALS-1001 - Implement folding range
• ALS-1002 - Implement selection range
• ALS-1063 - Support indentation configuration for styling suggestions

LSP 3.15:

• ALS-1124 - Analyze moving Lsp4j 0.9.0
• ALS-1125 - Analyze vscode-languageserver library for LSP 3.15
• ALS-1126 - Adop lsp4j 0.9 in als-client
• ALS-1127 - Adopt lsp4j 0.9

Stories:

• ALS-1050 - Create internal dialect registry and consume it from plugins
• ALS-1136 - Add "xx" status code suggestions
• ALS-1156 - Analyze als-client performance deltas
• ALS-1133 - Telemetry enhancements | Message types and synchronized Begin/End messages

Bugs:

• ALS-1130 - Validations missing in JSON file referenced in root
• ALS-1132 - Class cast exception when specifying ClientLogger to LanguageServer in JS
• ALS-1135 - Change category for oas 3.0 types facets
• ALS-1137 - Suggestions not honoring the root file location
• ALS-1138 - Upper level folder suggestions not working
• ALS-1139 - Suggestions does not include application/xml in OAS 3 spec
• ALS-1140 - Suggestion fails in empty file (one curly bracket only)
• ALS-1141 - Incorrect suggestion for the context
• ALS-1144 - Indentation fails for selected suggestion (json)
• ALS-1151 - Suggestions do not provide any option when defining schema example
• ALS-1160 - Missing validation errors when including RAML fragments in a RAML 0.8