Thank you for filing a gopls issue! Please take a look at the Troubleshooting guide, and make sure that you have provided all of the relevant information here.

Please post the literal text instead of an image, as the latter makes it much more difficult to read. The error text in the image states:

You are neither in a module nor in your GOPATH. If you are using modules, please open your editor at the directory containing the go.mod. If you believe this warning is incorrect, please file an issue: https://github.com/golang/go/issues/new.

However the file tree shows a go.mod file next to main.go

@mytea003: It looks like you've opened a directory above the go.mod file, but gopls currently requires you to open your module as the root directory. To work around this, you can use VS Code's File -> Add Folder to Workspace feature for the officeCode folder. We are working on making this work better for gopls/v0.5.0.

@mytea003: It looks like you've opened a directory above the go.mod file, but gopls currently requires you to open your module as the root directory. To work around this, you can use VS Code's File -> Add Folder to Workspace feature for the officeCode folder. We are working on making this work better for gopls/v0.5.0.

How do I do it step by step?As you can see from the picture, I have added the project to the workspace.

I think the folder is a subdirectory of your top-level workspace directory. You need to add folder explicitly to the workspace, which can be done by clicking the "File" menu and then selecting "Add Folder to Workspace". You can then select the officeCode folder. Once it's added, gopls should work as expected.

I think the folder is a subdirectory of your top-level workspace directory. You need to add folder explicitly to the workspace, which can be done by clicking the "File" menu and then selecting "Add Folder to Workspace". You can then select the officeCode folder. Once it's added, gopls should work as expected.

I see. After testing, we got the expectation.But I thought it was strange.Adding the current go.mod directory directly to the workspace is expected.But according to my previous method, there are certain items that can also get the expected (hover message), so is this a BUG of gopls?

That warning is meant to indicate that all of the features of gopls won't necessarily work, but some may, which is probably why you were seeing hovers. We are working on fixing this for the next release of gopls (https://github.com/golang/go/milestone/138), so the user experience will be smoother then. I'll close this issue since we're working on it.

That warning is meant to indicate that all of the features of gopls won't necessarily work, but some may, which is probably why you were seeing hovers. We are working on fixing this for the next release of gopls (https://github.com/golang/go/milestone/138), so the user experience will be smoother then. I'll close this issue since we're working on it.

thank you.Thank you again.