The purpose of the Language Server Index Format (LSIF) is it to define a standard format for language servers or other programming tools to dump their knowledge about a workspace. This dump can later be used to answer language server LSP requests for the same workspace without running the language server itself. Since much of the information would be invalidated by a change to the workspace, the dumped information typically excludes requests used when mutating a document. So, for example, the result of a code complete request is typically not part of such a dump.
A first draft specification can be found here.
> git clone this repository> npm install> npm run compile> npm run lsif-tsruns the indexer over the samples/typescript directory> npm run lsif-ts-allruns the indexed over the samples/typescript directory and pipes the output to the npm moniker rewriter.
Please note that the tools are work in progress and that we have not done any extensive testing so far. Known issues are:
- Go to Declaration for function overloads doesn't honor the signature
- Go to Type Declaration is not fully implement
- Document link support is completely missing
- Reference results are not always inlined when possible
There is also an extension for VS Code that can serve the content of a LSIF JSON file. Consider you have dumped the content of a workspace into an LSIF JSON file then you can use the extension to serve the supported LSP requests. This works as follows:
- follow the steps in 'How to Run the tools` above.
- clone the example you want to produce a index for into a sibling directory. For example https://github.com/Microsoft/vscode-uri.git.
- cd into the workspace folder of the example.
> npm install> node ..\language-server-index-format\tsc-lsif\lib\main.js --outputFormat=json -p src/tsconfig.jsonand pipe the output into a file. Note that under PowerShell you best do| Out-File -Encoding ASCII lsif.json> git clone https://github.com/Microsoft/vscode-lsif-extension.gitinto a sibling directory.> cd vscode-lsif-extension> npm install> npm run compile- open the workspace using code.
- switch to the debug viewlet and launch
Launch Client - open the example workspace, e.g.
vscode-uri. LSP requests like find all references or hover are served from the index dump.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT License.
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
Privacy information can be found at https://privacy.microsoft.com/en-us/
Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.