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
Currently, we don’t support the Language Server Protocol (LSP) directly. However, we leverage the underlying language server implementations from the VSCode HTML and CSS language servers. This allows us to provide language intelligence for HTML and CSS with VSCode’s capabilities, while also adding our own layer of code intelligence.
For JavaScript (JS) and TypeScript (TS), we currently rely on our own code intelligence from "Brackets". We plan to transition to a language server-based implementation for JS and TS within the next 2/3 releases. Our priority is to deliver the best out-of-the-box code intelligence for the web, which is currently more feasible with language servers, without implementing the full LSP specification.
Since adopting the LSP standard alone wouldn’t significantly improve workflows (as long as the underlying language server is implemented anyway), we’ve chosen to prioritize practical performance improvements over full LSP compliance. But, we aim to incorporate full LSP support soon after we roll out JS/TS language server integration in 2 to 3 releases.
Please add PHCode to this list if relevant https://microsoft.github.io/language-server-protocol/implementors/tools/
Any code editor not on that is not a serious code editor.
PHCode is the descendant of Brackets.
Source:
So even without using it I guess it should be on that list.
The text was updated successfully, but these errors were encountered: