2 ms·
I've never had the need to rename anything in vendor/, so I can't really answer here. I've only renamed stuff in my project's internal/. Can I ask you why did
by ainar-g 7y ago
I've never had the need to rename anything in vendor/, so I can't really
answer here. I've only renamed stuff in my project's internal/. Can
I ask you why did you feel the need to rename something in your vendor/?
It feels completely unnecessary and counter-intuitive to me.
- Groxx 7y agoSorry, I meant "does it only try to use my GOPATH for imports while type-checking my source". My dependencies are in ./vendor, so ignoring it would lead to lots of problems. Renaming stuff in vendor: almost never. It could be useful for handling library updates though, if it worked and were possible: you could refactor it to the v2 path, automatically updating your code, and then pull the new update for real and be mostly done (for minor-but-breaking changes). I've done similar things in other systems for library updates, since there's usually zero automated migration help for library users, only authors, despite users greatly outnumbering the authors.
- ainar-g 7y agoAh, I see. As far as I know it is vendor-directory-aware. At least it always renamed my packages that imported stuff from vendor/ with no problems. I don't deny that you could have issues with the tool, I simply have never encountered any myself.