-
Notifications
You must be signed in to change notification settings - Fork 5
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
Doesn't work with non-root go.mod #10
Comments
Thanks for the report! This is a |
@stamblerre Thanks for replying so fast and sorry the late response. I was glancing through the issues for |
No problem! The issue for the warning is golang/go#37279, and a number of the issues related to the workspace management are actually now in the |
Looking at golang/go#32394 I came across this your comment about adding a Workspace folder for each module. I think this is a good band-aid till |
The workspace folders are typically handled at the level of the editor (for example, in VS Code, you can add a folder to a workspace via |
Thanks for the feedback! I'm gonna look into implementing it later this week when I have some time. I broke workspace configuration into its own issue, #11 |
First, I'd like to say thanks for putting this together! I really enjoy using it for all my Go projects but I have discovered an issue when I have a non-root go.mod. For example, let's say the given structure of a project is:
Currently, if I open on the
main.go
file insidemy-awesome-tool
the following message appears:Not sure if this is an issue with
ide-gopls
orgopls
itself but I figured I'd start here and see if anyone else has ran into the same problem.The text was updated successfully, but these errors were encountered: