Skip to content
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

chore: simplify and refactor linting #12318

Merged
merged 11 commits into from
Jun 21, 2022
Merged

chore: simplify and refactor linting #12318

merged 11 commits into from
Jun 21, 2022

Conversation

alexanderbez
Copy link
Contributor

@alexanderbez alexanderbez commented Jun 21, 2022

Description

  • Use tools methodology to use canonically versioned tools/binaries (e.g. golangci-lint)
    • This makes it so that all environments and developers use the same versions of tools (no need to rely on hacky docker containers)
  • Update makefile
  • Address linting errors

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • added ! to the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic
  • reviewed API design and naming
  • reviewed documentation is accurate
  • reviewed tests and test coverage
  • manually tested (if applicable)

@github-actions github-actions bot added the C:x/genutil genutil module issues label Jun 21, 2022
@alexanderbez
Copy link
Contributor Author

@roysc just an FYI -- there's a bunch of linting errors in store/v2alpha1/multi/test_util.go and related files in the package.

@github-actions github-actions bot added the C:Keys Keybase, KMS and HSMs label Jun 21, 2022
@alexanderbez alexanderbez marked this pull request as ready for review June 21, 2022 16:13
@alexanderbez alexanderbez requested a review from a team as a code owner June 21, 2022 16:13
Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tACK

@tac0turtle tac0turtle added the A:automerge Automatically merge PR once all prerequisites pass. label Jun 21, 2022
@mergify mergify bot merged commit c6315ec into main Jun 21, 2022
@mergify mergify bot deleted the bez/tools branch June 21, 2022 17:49
@roysc
Copy link
Contributor

roysc commented Jun 22, 2022

@alexanderbez thanks, is there a CI run that shows those errors? I don't see anything when running the linter locally.

@alexanderbez
Copy link
Contributor Author

@alexanderbez thanks, is there a CI run that shows those errors? I don't see anything when running the linter locally.

That's because I had to add // nolint:... to all of them to silence them. Grep for // nolint in those packages and you'll see everything I had to silence and they should be addressed 👍

larry0x pushed a commit to larry0x/cosmos-sdk that referenced this pull request May 22, 2023
## Description

- Use tools methodology to use canonically versioned tools/binaries (e.g. golangci-lint)
  - This makes it so that all environments and developers use the same versions of tools (no need to rely on hacky docker containers)
- Update makefile
- Address linting errors

---

### Author Checklist

*All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.*

I have...

- [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] added `!` to the type prefix if API or client breaking change
- [ ] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting))
- [ ] provided a link to the relevant issue or specification
- [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/building-modules)
- [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing)
- [ ] added a changelog entry to `CHANGELOG.md`
- [ ] included comments for [documenting Go code](https://blog.golang.org/godoc)
- [ ] updated the relevant documentation or specification
- [ ] reviewed "Files changed" and left comments if necessary
- [ ] confirmed all CI checks have passed

### Reviewers Checklist

*All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.*

I have...

- [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] confirmed `!` in the type prefix if API or client breaking change
- [ ] confirmed all author checklist items have been addressed 
- [ ] reviewed state machine logic
- [ ] reviewed API design and naming
- [ ] reviewed documentation is accurate
- [ ] reviewed tests and test coverage
- [ ] manually tested (if applicable)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants