[bugfix] add go work use project_name
If the go.work file exists in the parent directory after the project is created, but the project directory is not added, it will cause the situation that go list -json -m in the current workspace does not return new project info
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 94.25%. Comparing base (
7568674) to head (6e757e7). Report is 556 commits behind head on master.
Additional details and impacted files
If the
go.workfile exists in the parent directory after the project is created, but the project directory is not added, it will cause the situation thatgo list -json -min the current workspace does not return new project info
What about the parent's parent dir? Like go mod tidy, The best solution is to handle it manually.
If the
go.workfile exists in the parent directory after the project is created, but the project directory is not added, it will cause the situation thatgo list -json -min the current workspace does not return new project infoWhat about the parent's parent dir? Like
go mod tidy, The best solution is to handle it manually.
If it can be handled manually, I will not submit this PR.
function getRealModule will return no matched module.