-
Notifications
You must be signed in to change notification settings - Fork 185
Server is not parsing all php files with other extensions. #145
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
Comments
|
Perhaps, we could have a "valid PHP file extensions" (similar to CodeSniffer) configuration sent by the client. |
IMHO this is a real shortcoming in the protocol... the IDE should be the one to decide which files the language server needs to see. Not the other way around. |
How can the IDE know what files the LS needs? |
Right now it can't. But this was more a thought about extending the LSP. The LS could announce to the client the language(s) it supports and have the client send it a list of paths/file contents to parse. Most editors have a global map of suffix-->language after all. |
It's not as simple as that. LS don't only need files like |
With #136 excludes works? I have this settings.json :
but app/cache folder is parsed. I'm executing version 3.0.1
|
Is it still the case that we can't configure which file extensions are handled? |
I think the server is not parsing all files which are set to be php language files. I am basing this overvation on the fact that I do not see any of these files in the language server output when it is parsing all of the files.
This would be helpful because some of us may have .inc files, and also .module files set to the php language. This is because Drupal and some of it's modules are using these extensions. Maybe we could query VS code for all files set to php language and include them as well.
Thanks!
The text was updated successfully, but these errors were encountered: