You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now vendoring use repository naming as-is for names with uppercase, while module cache in $GOMODCACHE use exclamation mark for uppercase
This vendor behavior cause inconsistent behavior on different case systems
Idea: new flag for go mod vendor that change produced folder names from AbCd to !ab!cd
Let's imagine two packages
example.com/organization/project1
example.com/Organization/project2
Go version
go version go1.23.6 linux/amd64
Output of
go env
in your module/workspace:What did you do?
Now vendoring use repository naming as-is for names with uppercase, while module cache in
$GOMODCACHE
use exclamation mark for uppercaseThis vendor behavior cause inconsistent behavior on different case systems
Idea: new flag for
go mod vendor
that change produced folder names from AbCd to !ab!cdLet's imagine two packages
example.com/organization/project1
example.com/Organization/project2
Current go modules cache behavior
Reproduce: https://github.com/psydvl/goVendorRepro
What did you see happen?
Current go mod vendor behavior on case-sensitive system
Current go mod vendor behavior on case-insensitive system
What did you expect to see?
The text was updated successfully, but these errors were encountered: