Lucas Bremgartner

See https://github.com/OpenPeeDeeP/depguard/issues/9#issuecomment-657441364 for a hint, on how these situations can be detected by the depguard linter (also included in golangci-lint).

I guess, for this case we can warn, but we can not always give the correct fix to the user. So I would expect the linter to provide a meaningful...

@cch123 I am not sure, if you still follow this issue, since it has been several years since you raised it. But in https://github.com/mna/pigeon/pull/123 we have a PR, that fixes...

@cch123 Yes, it is known, that the master branch has this limitation. Do you mind to checkout the code from PR #123?

@kpacha Thanks for opening the issue. A quick updated from my end: we ended up replacing this package in our KrakenD API GW with our own implementation for the prometheus...

Hi @suadev, we used Grafana for the visualization of the results. That being said, I have no longer access to these dashboards.

@LandonTClipp Yes, it is possible to have multiple mock implementations (from different interfaces) in a single file. given a file: ```go package file type Foo interface { Bar() } type...

Hi @LandonTClipp I did some initial tests and it looks like I am failing to reproduce my mocks with mockery. Currently I am facing the following issues: I have a...

> > Even with inpackage: True and outpkg: "{{.PackageName}}" set, the generated mock does contain an import for the package where the interface is defined, which obviously leads to an...

Hi @Raneddo Sorry for my slow response. I am not sure I can follow your proposal. Can you please give a code example with a description what you expect to...