Loading
chore: change ls node bundle path logic
Description
This MR changes LS node bundle path resolution logic to support gitlab-org/editor-extensions/gitlab-lsp#1461 (closed)
Here's the related MR in the LS server: gitlab-org/editor-extensions/gitlab-lsp!2242 (merged)
Related Issues
Resolves #2117 (closed)
How has this been tested?
- run the vscode-extension and check that the webviews and code suggestions are working as expected.
- checkout gitlab-org/editor-extensions/gitlab-lsp!2242 (merged)
- run
npm run watch -- --editor=vscodein gitlab lsp - run the vscode-extension and check the webviews and code suggestions are working as expected.
-
If src/browserorsrc/commonhas been modified, please consider interoperability with the Web IDE. See Running the Extension in WebIDE. -
Consider an end-to-end test for significant new features that aren't covered by integration tests.
Screenshots (if appropriate)
What CHANGELOG entry will this MR create?
-
fix:Bug fix fixes - a user-facing issue in production - included in changelog -
feature:New feature - a user-facing change which adds functionality - included in changelog -
BREAKING CHANGE:(fix or feature that would cause existing functionality to change) - should bump major version, mentioned in the changelog -
None - other non-user-facing changes
Edited by Andrei Zubov