3 ms·
It seems that Language Server Index Format (LSIF) https://code.visualstudio.com/blogs/2019/02/19/lsif https://code.visualstudio.com/blogs/2019/02/19/lsif is the
by sytse 7y ago
It seems that Language Server Index Format (LSIF) https://code.visualstudio.com/blogs/2019/02/19/lsif https://code.visualstudio.com/blogs/2019/02/19/lsif is the successor to the Language Server Protocol (LSP). LSIF supports code navigation without having all source code files available on a local disk like LSP requires.
- kdmarrett 7y agoGood to know thank you
- mikewhy 7y agoMaybe "successor" isn't the right word, as per the linked article: > The goal of the Language Server Index Format is to augment the LSP protocol
- sytse 7y agoThanks for making that clear.
- lostintangent 7y agoCorrect! We designed LSIF to be a complement to LSP. LSIF is basically a way to persist language server state, so that LSP queries (e.g. what are the definitions for this symbol?) can be answered without needing an active LSP server running. Among other things, LSIF enables rich IDE navigations on remote codebases, where’s its much more scalable to perform those queries using indexed data vs. spinning up language servers. Here’s the blog post where we first announced the work we were doing, that led to the creation of LSIF: https://code.visualstudio.com/blogs/2018/12/04/rich-navigation https://code.visualstudio.com/blogs/2018/12/04/rich-navigati....
- slimsag 7y agoAt Sourcegraph we are also running an identical website but for tracking LSIF indexers :) https://lsif.dev https://lsif.dev