LSP4E 0.26.5 Released

[rubenporras]

New features

• Add diagnostic code as suffix to marker message by @sebthom in feat: add diagnostic code as suffix to marker message #1065
• Make diagnostic marker messages configurable by @sebthom in feat: make diagnostic marker messages configurable #1066
• Add hide fields toolbar button to outline view (fix Add "hide fields" filter to outline view's toolbar #1073) by @travkin79 in Add hide fields toolbar button to outline view (fix #1073) #1075
• Allow access to CodeAction in CodeActionMarkerResolution. by @andrewL-avlq in Allow access to CodeAction in CodeActionMarkerResolution. #1087
• Introduce LanguageServerWrapper#getServerCapabilitiesAsync by @sebthom in feat: introduce LanguageServerWrapper#getServerCapabilitiesAsync #1098

Performance improvementes

• Improve StreamProxyInputStream by @sebthom in perf: improve StreamProxyInputStream #1068
• Improve DSPLaunchDelegate debug adapter monitor performance by @sebthom in perf: improve DSPLaunchDelegate debug adapter monitor performance #1080

Fixes

• DocumentInputStream does not handle surrogate pairs correctly by @sebthom in fix: DocumentInputStream does not handle surrogate pairs correctly #1069
• Memory leak in EditorToOutlineAdapterFactory by @sebthom in fix: memory leak in EditorToOutlineAdapterFactory #1081
• Potential race condition in LSPProgressManager#report by @sebthom in fix: potential race condition in LSPProgressManager#report #1085
• Don't log same BadLocationException excessively by @sebthom in fix: don't log same BadLocationException excessively #1083
• Respect inlayhint padding by @BoykoAlex in Respect inlayhint padding #1089
• Fix disappearing sort button in outline view (fix Sort toolbar button disappears in outline view if an LSP editor is activated #1091) by @travkin79 in Fix disappearing sort button in outline view (fix #1091) #1092
• Fix NPE seen in GitHub Actions runs by @rubenporras in fix NPE seen in GitHub Actions runs #1096
• Adapt resolveCodeAction to handle timeout and interrupted exception by @rubenporras in fix: Adapt resolveCodeAction to handle timeout and interrupted exception #1099
• Propagate LanguagServerWrapper startup exception correctly by @ava-fred in fix: propagate LanguagServerWrapper startup exception correctly #1044

Code improvements

• Enable NonNullByDefault for lsp4e.debug and lsp4e.jdt plugins by @sebthom in refact: enable NonNullByDefault for lsp4e.debug and lsp4e.jdt plugins #1060
• Make tm4e an optional dependency by @sebthom in refact: make tm4e an optional dependency #1064
• Resolve sonar findings by @sebthom in refact: resolve sonar findings #1067
• Remove duplicate code from lsp4e.debug by @sebthom in refact: remove duplicate code from lsp4e.debug #1071
• Use var keyword and List.of and Set.of where applicable by @sebthom in refact: Use var keyword and List.of and Set.of where applicable #1072
• Use LS.withCapability() instead of LS.withFilter() if applicable by @sebthom in refact: use LS.withCapability() instead of LS.withFilter() if applicable #1077
• Cleanup SupportedFeatures class by @sebthom in refact: cleanup SupportedFeatures class #1076
• Improve handling of arrays by @sebthom in refact: improve handling of arrays #1079
• Remove duplicate null check by @rubenporras in refactor: remove duplicate null check #1084
• Improve code reuse by @rubenporras in refactor: improve code reuse #1082
• Remove unnecessary launcherFuture.isCancelled() check by @sebthom in refact: remove unnecessary launcherFuture.isCancelled() check #1090
• Improve null analysis by @sebthom in refact: improve null analysis #1095

Build improvements

• Mask manually entered Dash Token by @sebthom in ci: mask manually entered Dash Token #1097

Upgraded libraries

• Update Highlight.js to 11.10.0 by @vrubezhny in Update Highlight.js to 11.10.0 #1047

Full Changelog: 0.26.4...0.26.5

---

This discussion was created from the release 0.26.5.

[sebthom]

@rubenporras Just a quick question about release numbers. Wouldn't new features warrant a bump of the minor version?

[rubenporras]

Since we intentionally do not use the three numbers of the release version (we stay at version 0, as far as I recall @mickaelistria wanted to stay so to indicate that the API is not fully stable), I am following the semantic versioning with some liberty, using the schema 0.MAJOR.MINOR. That is why I bumped the last number.

I would be okay to release 1.0.0 and use normal semantic versioning in the future.

[sebthom]

I don't mind staying on 0.x for now. Thanks for clarification.