3 ms·
You can directly edit the downloaded code when using modules, you don’t need your go.work flow at all. I often do it while debugging particularly weird bugs or
by peter_l_downs 2y ago
You can directly edit the downloaded code when using modules, you don’t need your go.work flow at all. I often do it while debugging particularly weird bugs or to better understand library code I’m using.
- metaltyphoon 2y agoIts much better to do go.work and add to your ignore. This way you won’t have to muck with go.mod and commit the file with local replaces
- gwd 2y agoOne way or another, the current workflow has to be: 1. Download the code (or update the copy you downloaded last time you had an issue) 2. Redirect `go build` to use the downloaded copy rather than the upstream copy (either by modifying go.mod or go.work) 3. Do the editing 4. Undo #2 Under the old system, you just had to do #3. And sure, it's not that much work, but it's a bit more than I had to do before.
- peterldowns 2y agoYou can just edit the copy that ‘go get / go build’ download to your system. Afterwards undo the edits or re-download the module to wipe out your edits. No need to use go.work, local replaces, or anything. The files are on your disk!