ralf-cestusio
ralf-cestusio
The idea of writing "plugins" for the syncher is great i think. It will keep configuration simple and transparent and at the same time allow us to write custom syncers...
you are missing the go.mod file in the v2 directory. so the step from the blog looking like ``` $ cp go.mod v2/go.mod $ go mod edit -module github.com/googleapis/gax-go/v2 v2/go.mod...
I would agree that it is the best long term solution. The go team has changed their mind about how to deal with modules and module versions multiple times. Using...
Sounds good! Its a good driving factor to get ppl to use v2 when it comes out. The downside of this is that i will have to temporarily move our...
i have a poc in https://github.com/magicmoose/ginkgo/tree/no_module_cross but realised that i was using a go 1.16+ feature. I will have to find some time to rewrite that against 1.15. But feel...
I totally missed this message. I will go give it a try in the (hopefully) near future. I think the behavior you are seeing is the now default go behavior:...
I have seen something similar in my case (But there the problem stems from the fact that ginkgo executes tests over module boundaries. see also https://github.com/onsi/ginkgo/issues/801 So in my case...
There is no solution yet (at least to my knowledge)
This workaround will also not work if you try to generate while using workspaces
I can remember this from a time before wire was calling -mod=mod. It was because of a "user error" in a project which is using wire. Wire is not included....