This is a good illustration of something I've been concerned about for a
while: the fact that pulling in a package also pulls in all testing
dependencies of that package recursively.
To take github.com/hashicorp/vault/api as an example, I made this little
module:
-- main.go --
pac
go list ./...
пятница, 18 января 2019 г., 1:26:02 UTC+3 пользователь Francis Chuang
написал:
>
> Thanks, Justin and Harmen.
>
> I deleted my go.mod and go.sum, then ran "go mod init ..." and "go test".
> The list of dependencies in go.mod and go.sum is now a lot slimmer. I tend
> to run my test
Thanks, Justin and Harmen.
I deleted my go.mod and go.sum, then ran "go mod init ..." and "go test".
The list of dependencies in go.mod and go.sum is now a lot slimmer. I tend
to run my test suites in a bunch of docker containers, so "go test" fails
for me when blindly executed from the root of
On Fri, Jan 18, 2019 at 07:18:41AM +1300, Justin Israel wrote:
> On Fri, Jan 18, 2019, 12:36 AM Francis Chuang wrote:
>
> > Hey everyone,
> >
> > I was wondering if I can get some ideas on how to solve this dependency
> > problem with Go modules. I am using Go 1.11.4 on Linux (Windows Subsystem
>
On Fri, Jan 18, 2019, 12:36 AM Francis Chuang wrote:
> Hey everyone,
>
> I was wondering if I can get some ideas on how to solve this dependency
> problem with Go modules. I am using Go 1.11.4 on Linux (Windows Subsystem
> for Linux to be exact).
>
> The first part of the problem is that for one
Hey everyone,
I was wondering if I can get some ideas on how to solve this dependency
problem with Go modules. I am using Go 1.11.4 on Linux (Windows Subsystem
for Linux to be exact).
The first part of the problem is that for one of my libraries, I am
importing github.com/hashicorp/vault/api,
