-
Notifications
You must be signed in to change notification settings - Fork 761
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
test: add a test for file watching API with gopls #404
Comments
Change https://golang.org/cl/244605 mentions this issue: |
I noticed this wasn't working correctly when debugging issues with file changes on disk. I think I misunderstood how to correctly match on zero or more path segments. Confirmed that this is working as expected with VS Code, but we really need regression tests for this in VS Code (it seems to be based directly on VS Code's API). Filed golang/vscode-go#404. Change-Id: Ib906f73a97317dfa9bd30099877c90d4072651cc Reviewed-on: https://go-review.googlesource.com/c/tools/+/244605 Run-TryBot: Rebecca Stambler <rstambler@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com>
Change https://golang.org/cl/247684 mentions this issue: |
This is a work-around for microsoft/vscode#104387. We now always lowercase the drive letter on Windows. This CL also fixes a bug introduced by CL 245327, which caused URIs to be used instead of paths in the GlobPattern. We really need VS Code integration tests for this (golang/vscode-go#404). Updates golang/go#40661 Change-Id: I21be6d929288cfe41168cea34001fc2f41ac6c8b Reviewed-on: https://go-review.googlesource.com/c/tools/+/247684 Run-TryBot: Rebecca Stambler <rstambler@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
Change https://golang.org/cl/251081 mentions this issue: |
Removing this from the vscode-go: gopls by default project because this is not a blocker, though we should have these tests in place before (if ever) |
A file watching integration test would be really useful, since the LSP file watching API is based on VS Code's.
The text was updated successfully, but these errors were encountered: