feat: use go.work to reduce core library dependencies

[slsyy]

some shenaningas were introduced to run tests&lint over all modules Probably it won't be necessary, when
golang/go#71294 is resolved

[ccoVeille]

I'm unsure to understand why you are computing all modules then run sequentially via the matrix

For me, as long as you have a go.work, go test ./... and golangci-lint run ./... should work in a transverse way

So for me, you don't need the go list -json | jq

Could you break something dbtests/mysql_test.go either with code and style

Then try to run go test and golangci-lint

They should be detected.

It's worth trying

[slsyy]

For me, as long as you have a go.work, go test ./... and golangci-lint run ./... should work in a transverse way

Unfortunately it does not work in that way, you need to run go test in each go.mod directory, check this golang/go#71294

Anyway I am still experimenting and I will try few different ideas to check, which one least sucks

ty for your input

[ccoVeille]

For anyone interested

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.

Originally posted by @rsc in golang/go#71294 (comment)

🤞

[ccoVeille]

Unfortunately it does not work in that way, you need to run go test in each go.mod directory, check this golang/go#71294\n\nAnyway I am still experimenting and I will try few different ideas to check, which one least sucks

Hi @slsyy

While I'm now convinced about the lack of feature in go test, I'm doubtful about the fact golangci-lint doesn't support it

A few weeks ago, I added a simple go.work file in gofr framework

• chore: fix go.mod add go.work gofr-dev/gofr#1426

And all the errors appeared locally when I was running golangci-lint manually locally