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
Actual behavior A clear and concise description of what the bug is. The package comments are generated like this:
// mockgen -destination demo/mock.go -package demo . Demoer // // Package demo is a generated GoMock package. package demo
However, this is not correct, as it doesn't follow the package guidelines documented here: https://staticcheck.io/docs/checks#ST1000
Expected behavior A clear and concise description of what you expected to happen.
I expect the generated code to be:
This would follow the guidelines and make the linter happy too.
To Reproduce Steps to reproduce the behavior
mockgen -destination demo/mock.go -package demo . Demoer
Additional Information
source
Triage Notes for the Maintainers
Here's an attempt at fixing the issue: #112.
The text was updated successfully, but these errors were encountered:
Closing since #112 was merged. Thanks!
Sorry, something went wrong.
No branches or pull requests
Actual behavior A clear and concise description of what the bug is.
The package comments are generated like this:
However, this is not correct, as it doesn't follow the package guidelines documented here: https://staticcheck.io/docs/checks#ST1000
Expected behavior A clear and concise description of what you expected to
happen.
I expect the generated code to be:
This would follow the guidelines and make the linter happy too.
To Reproduce Steps to reproduce the behavior
mockgen -destination demo/mock.go -package demo . Demoer
on any interface/packageAdditional Information
source
Triage Notes for the Maintainers
Here's an attempt at fixing the issue: #112.
The text was updated successfully, but these errors were encountered: