alfa-alex

Ran into the same issue (`go.temporal.io/sdk v1.15.0`). What's your current position on this? Should the use of invocation count assertions be avoided at the moment?

Actually for my use-case there was a relatively simple fix to this: Calling `Test` on the `mock`. So, instead of the original ```go // NewTestWorkflowEnvironment creates a new instance of...

So you imply we should check the invocation count assertions via `env.GetWorkflowError()`? I thought that's what `env.AssertExpectations(t)` is for. The documentation reads: ```go // AssertExpectations asserts that everything specified with...

Yeah, it looks like a testify issue. I think it's been described here: https://github.com/stretchr/testify/issues/608. Thank you! --- Edit: To summarize, the invocation count assertions should probably best be avoided. Other...

> If I understand correctly, you are using something written in Go to integrate with the API Yes! > and rather than manually (re)define the structs you are simply importing...

This is indeed very useful. Exactly what I was looking for. Thanks for the fast response! Just as an example of how I am currently using it: ```go import "github.com/axllent/mailpit/storage"...

Perfectly valid reasoning. Go ahead. :+1: And thank you for all your efforts!

Awesome! Did the integration, it's all much cleaner now! :+1: Thank you!

This is strongly related to https://github.com/axllent/mailpit/issues/21 For convenience I don't define e.g. `apiv1.MessagesResult` myself but use it directly from the (imported) mailpit package. I know that many project struggle with...

I guess additionally tagging the versions using `v` is not an option either, is it? Let me just add that making "a `go.mod` a bit more readable" is a bit...