-
Notifications
You must be signed in to change notification settings - Fork 795
Issues: golang/vscode-go
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Is it possible that we have a parameter in settings to allow user specify the sub-directory as root of Go project
gopls/workspace
workspace setup related issues (UX of multi-modules, nested modules, GOPATH handling)
Question
This is a question, rather than an issue report.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
go.work: create a go.work automatically for a workspace with multiple modules
FeatureRequest
gopls/workspace
workspace setup related issues (UX of multi-modules, nested modules, GOPATH handling)
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
ux: suggest go.work if user is using go1.18+ and experimentalWorkspaceModule enabled
FeatureRequest
gopls/workspace
workspace setup related issues (UX of multi-modules, nested modules, GOPATH handling)
ux: suggest go.work if multiple modules are present in the repository
FeatureRequest
gopls/workspace
workspace setup related issues (UX of multi-modules, nested modules, GOPATH handling)
doc: tutorial for go.work (using vscode)
Documentation
gopls/workspace
workspace setup related issues (UX of multi-modules, nested modules, GOPATH handling)
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.