We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, maintainers! I would like to express my sincere gratitude for your efforts in maintaining gomock.
Requested feature Is the issue golang/mock#616 resolved? If not, i hope improvement the diffs when tests fails.
I didn't find out whether the problem resolved or not as the original repository has the issue archived and cannot ask there.
Why the feature is needed As showing the original issue, it is often hard to understand and interpret the diffs.
(Optional) Proposed solution i think we can solve this problem by using the method indicated in the following comments:
Alternatively, adding an option to change the default matcher may resolve this, as it would allow for the use of this way.
The text was updated successfully, but these errors were encountered:
The current diff output is pretty low readability. Would love to see the golang/mock#616 (comment) or something similar implemented.
Sorry, something went wrong.
No branches or pull requests
Hi, maintainers! I would like to express my sincere gratitude for your efforts in maintaining gomock.
Requested feature
Is the issue golang/mock#616 resolved? If not, i hope improvement the diffs when tests fails.
I didn't find out whether the problem resolved or not as the original repository has the issue archived and cannot ask there.
Why the feature is needed
As showing the original issue, it is often hard to understand and interpret the diffs.
(Optional) Proposed solution
i think we can solve this problem by using the method indicated in the following comments:
Alternatively, adding an option to change the default matcher may resolve this, as it would allow for the use of this way.
The text was updated successfully, but these errors were encountered: