Skip to content

fork updation#1

Open
sidradchandran wants to merge 1152 commits intosidradchandran:masterfrom
microsoft:master
Open

fork updation#1
sidradchandran wants to merge 1152 commits intosidradchandran:masterfrom
microsoft:master

Conversation

@sidradchandran
Copy link
Copy Markdown
Owner

No description provided.

ramya-rao-a and others added 30 commits July 5, 2019 19:25
ramya-rao-a and others added 25 commits April 24, 2020 23:27
This CL includes only HoverProvider tests, that use the same scenario
as the hover provider tests with godoc and gogetdoc in
integration/extension.test.ts.

Gopls test setup is complicated because gopls currently does not
work in a single-file mode nor support mono repos with multiple
modules. VS Code in test environment does not support dynamic
registration of workspace folders during testing.  So, the
workspace folder needs to be specified before the extension
host launches (by vscode-test.runTests or launch.json extensionHost
type tasks).

As a workaround, I use an empty directory and start the extension
host with the empty directory for a testing. Then, let the test
populate the directory with necessary files. This is not ideal;
file copy is slow and the use of the single workspace directory
prevents parallelized testing.

Commiting an empty directory to use as a scratch space is not
ideal either, but no worse than what vscode dev in my opinion.
https://github.com/microsoft/vscode/blob/master/.vscode/launch.json

I also considered shelling out the extension host launch
after creating a temp directory and using it as a workspace directory.
That may work inside test/runTest.ts, but complicates debugging
when sarting the test using launch.json.

Also passes '--user-data-dir' flag to prevent the tests from
using my personal vscode settings and interfere tests.

Change-Id: I7b064441720da5c89833afab35e8273de808cfad
* goImports: avoid collapsing new imports into pseudo import line

getTextEditForAddImport tries to insert a newly added package
into an existing import group. If no import group exists, it
tries to merge single line import statements and create a group.

In this process, import statements like

  import "C"

are pseudo imports and shouldn't be grouped with other imports.
This CL changes parseFilePrelude to detect such pseudo imports
and excludes such imports from the grouping logic.

Fixes #1701

* correct the file name

mac and vsccode ignored casing, but linux and git were unhappy.
The lint rule was changed since PR #3157
so the newly added code broke the lint test.

Change-Id: Ic58dfa62e19cb61600b45fe10b43811eb00bc28d
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/230297
Reviewed-by: Rebecca Stambler <rstambler@golang.org>
Change-Id: I38114cf28e5b0151266b0a0b62cd3ef9f85c7361
Change-Id: Ic1a6eb955ad9a2e4eab81771dd0c4471670e22fa
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.