9911fd13cc
Design Doc: https://goo.gl/9G9d9k The initial prototype consists of a few parts: The VS Code extension is now built using TypeScript. The build artifact is checked-in along side the extension. The extension now starts up the language server when it is activated. The path to the LS executable is configurable via VS Code settings. The language server is a separate executable. It adds a light-weight object model on top of a Json Parser for reading/writing LSP requests and responses. The current server is very much bare-bones featurewise: - Tell the client that the server can handle "goto definition" - Recompile when Torque files change - Goto definition support for Macros/Builtins, local variables and arguments. R=mathias@chromium.org, mvstanton@chromium.org, tebbi@chromium.org Bug: v8:8880 Change-Id: Ie9b433e64ee63e9aa757b6bf71e5d52beb15b079 Reviewed-on: https://chromium-review.googlesource.com/c/1494354 Reviewed-by: Michael Stanton <mvstanton@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Reviewed-by: Mathias Bynens <mathias@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#59960} |
||
---|---|---|
.. | ||
.vscode | ||
out | ||
src | ||
syntaxes | ||
.npmrc | ||
language-configuration.json | ||
package.json | ||
README.md | ||
tsconfig.json | ||
tslint.json |
Torque support
This extension adds language support for the Torque language used in V8.
Installation
Since the extension is not published to the marketplace, the easiest way to install the extension is to symlink the extension to your local extension directory:
ln -s $V8/tools/torque/vscode-torque $HOME/.vscode/extensions/vscode-torque
Language server
The language server is not built by default. To build the language server manually:
autoninja -C <output dir> torque-language-server
The default directory where the extension looks for the executable is "out/x64.release",
but the absolute path to the executable can be configured with the torque.ls.executable
setting.