-
Notifications
You must be signed in to change notification settings - Fork 5.8k
fix(lsp): lsp should respect include/exclude files in format config #12876
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
Conversation
cli/main.rs
Outdated
| specifier_to_file_path(&config_file.specifier) | ||
| .ok() | ||
| .map(|p| p.to_str().map(|s| s.to_string())) | ||
| .flatten() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like it would be better to just do config_file.specifier.to_string() here? I didn't want to introduce a breaking change on this key though. Thoughts?
Edit: If we ever introduced remote configs then we would need to change this to just use the specifier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That change seems reasonable 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. Done in 1eaf50a
It is cleaner.
bartlomieju
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
fbb16b5 to
1eaf50a
Compare
Also changes it so the LSP sticks with module specifiers in the config file. I ran into an issue on CI with Mac where it was canonicalizing the file path of the config file and causing issues because now the config file was at a "different place" relative to potentially open files that aren't necessarily on the file system.
Closes #12865
Closes #12877