-
Notifications
You must be signed in to change notification settings - Fork 19
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
Integrate GolangCI-Lint #45
Comments
I would like to pick this up and give it a go 😄 |
@hanzei
Since the permissions are hardcoded, should those be changed?
The body is closed in this function
These from my understanding can be ignored as we are using the packages for user-hash generation and not encryption(i might be wrong)
On this error I am unsure wether to change the signature or not |
Thanks for jumping on this issue @arshchimni 👍 1.Yes, please change the permission to |
Mattermost is currently in the process of using
golangci-lint
as the default linter for all go projects. mattermost-community/mattermost-plugin-autolink#108 serves as an example of how the migration should look like:.golangci.yml
from https://github.com/mattermost/mattermost-plugin-autolink/ into this repository.Makefile
from https://github.com/mattermost/mattermost-plugin-autolink/ into this repository.build/
from https://github.com/mattermost/mattermost-plugin-autolink/ into this repository.go mod tidy
andmake dist
to ensure the build system works fine.linters-settings.goimports.local-prefixes
to the go module path i.e. github.com/mattermost/mattermost-plugin-aws-SNS
.make golangci-lint
and fix all issues that arise.Fixing an linter issue is sometimes trivial but can also be quite complicated. There might be cases, where ignoring an issue using
issues.exclude-rules
is needed. If you don't know how to resolve an error, please reach out to@hanzei
on the Mattermost Community Server or ask the question here.The text was updated successfully, but these errors were encountered: