3 ms·
LSP has addressed the editor code nav problem, but not the "just works in my web browser across all my code and multiple revisions" problem or the "let me build
by beyang 4y ago
LSP has addressed the editor code nav problem, but not the "just works in my web browser across all my code and multiple revisions" problem or the "let me build on top of a structured representation of code to enhance all my dev tools" problem. LSP's sister protocol LSIF aims to address the indexed code nav use case, but Steve calls out some of its shortcomings in the post, and these motivated our development of a new protocol, SCIP: https://about.sourcegraph.com/blog/announcing-scip https://about.sourcegraph.com/blog/announcing-scip
- bb010g 4y agoOn SCIP support–is there an index like <https://lsif.dev/ https://lsif.dev/>, <https://langserver.org/ https://langserver.org/>, or <https://microsoft.github.io/debug-adapter-protocol/implementors/adapters/ https://microsoft.github.io/debug-adapter-protocol/implement...> for tooling using SCIP? (It doesn't have to be as fancy as those. A wiki page on <https://github.com/sourcegraph/scip https://github.com/sourcegraph/scip> would be fine.)
- typesanitizer 4y agoCreated a PR to mention tools using SCIP in the README. https://github.com/sourcegraph/scip/pull/101 https://github.com/sourcegraph/scip/pull/101