Unnecessary Ginkgo dependency in go mod

[unmarshall]

Gomega can be used with or without Ginkgo. Using BDD styled testing frameworks is a personal choice and i for one find it quite difficult to read test cases that are written in Ginkgo. I just prefer using standard golang native test framework along with a minimalist assertion library.

I was hoping to use gomega as it works also with go native tests but unfortunately i do not wish to pull in ginkgo as a dependency which i am forced to do as soon as i include gomega. I was really hoping that you would consider making the core assertion library as a separate go module which will be independent of ginkgo and then provide extensions for easy consumption in ginkgo.

[onsi]

hey there - i’ve honestly tried real hard to make sure gomega doesn’t have a direct dependency on ginkgo and… as far as I know. it doesn’t! just a test dependency which i would have expected to come up as an indirect dependency. i’m honestly unsure why go mod thinks ginkgo is a required direct dependency. it really shouldn’t be (and really isn’t!)