Thoughts on adding a call to get the "canonical" name from Go proxy during the project name mapping for Go projects? This could cut down on casing problems creating multiple Projects, but only for valid Go module projects. There is a noticeable lag when making this request and the proxy does not have a cached response so I think that is the main tradeoff here.
I think the proxy protocol specifies that for projects that do not use go.mod files it will just create a virtual go.mod with the original name passed back, which I think means this is still a problem for any name that comes in for a non module package.
Thoughts on adding a call to get the "canonical" name from Go proxy during the project name mapping for Go projects? This could cut down on casing problems creating multiple Projects, but only for valid Go module projects. There is a noticeable lag when making this request and the proxy does not have a cached response so I think that is the main tradeoff here.
I think the proxy protocol specifies that for projects that do not use
go.modfiles it will just create a virtualgo.modwith the original name passed back, which I think means this is still a problem for any name that comes in for a non module package.