You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Deprecate api endpoint
* Switch npm version to v24 lts
* Update eslint dependency version
* Refactoring
* Move languages to separate file
* re enabled getTreeForUri
* Make get tree synchronous again
If you'd like to add support for a new language, see the [Adding a new language](#adding-a-new-language) section below. Alternatively, your extension can register a custom language with this extension. Although this is not the preferred way to add a new language, it can be convenient when you have a parser that you don't believe belongs in the main extension.
26
-
27
-
Parsing your own language is as simple as registering your `languageId` with an absolute path to your `.wasm` file:
It's straightforward to add any [language with a tree-sitter grammar](https://tree-sitter.github.io/tree-sitter/).
44
32
45
33
1. Add a dependency on the npm package for that language in [tree-sitter-wasms](https://github.com/cursorless-dev/tree-sitter-wasms)
46
-
2. Add a language to the dictionary at the top of `./src/extension.ts`
34
+
2. Add a language to the map in [`languages.ts`](./src/languages.ts)
47
35
3. Add a reference to `onLanguage:yourlang` to the [activationEvents section of package.json](package.json). `yourlang` must be a [VSCode language identifier](https://code.visualstudio.com/docs/languages/identifiers).
48
36
4. Run `npm install` and `npm run compile`, then hit `F5` in VSCode, with this project open, to test your changes.
0 commit comments