-
-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
any thoughts on adapting gomega matchers to gomock.Matcher interface #451
Comments
now i'm using a simple wrapper like:
|
I was going to ask if a wrapper was working. That would be what I would recommend and how I would approach it. I could see adding a gomock adapter extension to gomega (something like |
that would be perfect. i'm also thinking about taking full advantage of mockgen or something like that. just like how it generates mock recorders, we should be able to extract struct types from input and output arguments and generate strong typed structure matchers. that will be a lot better than the map we used for |
i'm heads down working on ginkgo 2.0 these days but making it easier to build custom marchers in gomega is something i'm interested in working on next. if you have bandwidth and are up for a PR I'd be happy to to pull in a gomock adapter and to take a look at a matcher generator with you! |
@onsi sure. i will take some time to walk through the codebase and see what i can do. |
so we can use them as gomock EXPECT arguments. the original matchers of gomock is too weak when dealing with complex types and assertions.
The text was updated successfully, but these errors were encountered: