Replies: 4 comments
-
Thoughts:
|
Beta Was this translation helpful? Give feedback.
-
Language server can also be a great conceptual choice to structure your code where "main" functionalities goes to the server and the vscode plugin will just be client making those functionalities available to vscode users. And you can of course just continue maintaining the vscode plugin and can let other editor communities maintainer their own "plugin"/client. This is the direction Tailwind have taken: https://github.com/tailwindlabs/tailwindcss-intellisense. |
Beta Was this translation helpful? Give feedback.
-
yeah i understand the value behind LSP. ultimately, @felixhaeberle's decision. but lsp will likely not lead to third party sherlock extensions. the majority of code in sherlock doesn't concern itself with LSP related features |
Beta Was this translation helpful? Give feedback.
-
I'm open to discussing this further, but I don't see a value in this right now. Converting it to a discussion. |
Beta Was this translation helpful? Give feedback.
-
Originally requested in i18n-ally but found out that it's not getting maintained these days.
lokalise/i18n-ally#1146
But overall having a language server allow support to other editors that has LSP support.
Beta Was this translation helpful? Give feedback.
All reactions