-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opening up the ServerDefinition to all languages #339
Comments
You can add a property in your plugin and make it configurable by end user |
But then the end user would themselves have to list every single individual extension they want to support ? |
Yes. Also there are file watches created for files with this extensions so plugin can handle file modifications and send events to the language server. |
No, but it's annoying to have to maintain a list of the 50+ extensions we support. The extensions we don't support are somewhat rare and usually wouldn't exist within our company's repository so it's safe to assume that it would indeed handle pretty much any file opened. ... but yes, obviously the better thing to do is indeed to list each extension. |
It would be great if we wouldn't have to exhaustively declare all supported file types in the ServerDefinition.
The text was updated successfully, but these errors were encountered: