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
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
Language Server Protocol provides calls for many (possibly all) of the language analysis that Sourcetrail needs. There are now open source langservers for many different languages - sometimes multiple implementations for a single language.
It's possible that configuring Sourcetrail to use an existing language server could reduce the work of supporting a language down to a simple config file.
EDIT: If you're interested in general discussion about LSP and/or LSIF support in Sourcetrail (which would make this issue redundant), that's happening here: CoatiSoftware/Sourcetrail#685 . This issue is about implementing that support as an external framework usable by bindings.
The text was updated successfully, but these errors were encountered:
@LouisStAmour Thank you! It looks like that's the better issue to host the general LSP & LSIF discussion. I think I should keep this one open since it's about using LSP at the binding level rather than the Sourcetrail level, so anyone could implement it in their own binding, but I'll change the description accordingly.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Language Server Protocol provides calls for many (possibly all) of the language analysis that Sourcetrail needs. There are now open source langservers for many different languages - sometimes multiple implementations for a single language.
It's possible that configuring Sourcetrail to use an existing language server could reduce the work of supporting a language down to a simple config file.
EDIT: If you're interested in general discussion about LSP and/or LSIF support in Sourcetrail (which would make this issue redundant), that's happening here: CoatiSoftware/Sourcetrail#685 . This issue is about implementing that support as an external framework usable by bindings.
The text was updated successfully, but these errors were encountered: