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!: var-naming linter errors #12135

Merged
merged 9 commits into from
Jun 3, 2022
Merged

Conversation

faddat
Copy link
Contributor

@faddat faddat commented Jun 3, 2022

Description

This PR works towards #12133 and does a fumpt for consistency once sdk.Int is merged.

The suggested merge order is to begin with sdk.Int, merge in the various linter PR's one by one, and then finally merge the changes to CI from #12134


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)

@codecov
Copy link

codecov bot commented Jun 3, 2022

Codecov Report

Merging #12135 (495237e) into main (78e2e35) will decrease coverage by 0.34%.
The diff coverage is 97.93%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #12135      +/-   ##
==========================================
- Coverage   66.38%   66.03%   -0.35%     
==========================================
  Files         686      671      -15     
  Lines       72102    71040    -1062     
==========================================
- Hits        47862    46910     -952     
+ Misses      21544    21466      -78     
+ Partials     2696     2664      -32     
Impacted Files Coverage Δ
x/group/keeper/keeper.go 54.85% <33.33%> (ø)
x/auth/tx/service.go 69.69% <100.00%> (ø)
x/authz/keeper/keeper.go 70.47% <100.00%> (ø)
x/group/keeper/grpc_query.go 65.28% <100.00%> (ø)
x/group/keeper/msg_server.go 68.51% <100.00%> (ø)
x/group/keeper/tally.go 72.09% <100.00%> (ø)
x/nft/client/testutil/grpc.go 100.00% <100.00%> (ø)
depinject/simple.go
core/appconfig/config.go
depinject/config.go
... and 12 more

@faddat faddat changed the title chore: var-naming linter errors and a fumpt !chore: var-naming linter errors and a fumpt Jun 3, 2022
simapp/test_helpers.go Outdated Show resolved Hide resolved
Copy link
Member

@tac0turtle tac0turtle left a comment

Choose a reason for hiding this comment

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

LGTM, left one comment

simapp/test_helpers.go Outdated Show resolved Hide resolved
@julienrbrt julienrbrt changed the title !chore: var-naming linter errors and a fumpt chore!: var-naming linter errors and a fumpt Jun 3, 2022
@julienrbrt julienrbrt changed the title chore!: var-naming linter errors and a fumpt chore!: var-naming linter errors Jun 3, 2022
@julienrbrt julienrbrt added the A:automerge Automatically merge PR once all prerequisites pass. label Jun 3, 2022
@mergify mergify bot merged commit b7097c3 into cosmos:main Jun 3, 2022
@blushi
Copy link
Contributor

blushi commented Jun 29, 2022

@marbar3778 @alexanderbez wondering if we should backport this to 0.46, there are var naming linting fixes in x/group (this is what caused the conflicts on #12381)

@alexanderbez
Copy link
Contributor

@Mergifyio backport release/v0.46.x

@mergify
Copy link
Contributor

mergify bot commented Jun 30, 2022

backport release/v0.46.x

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jun 30, 2022
## Description

This PR works towards #12133 and does a fumpt for consistency once sdk.Int is merged.

The suggested merge order is to begin with sdk.Int, merge in the various linter PR's one by one, and then finally merge the changes to CI from #12134

---

### 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...

- [x] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [x] added `!` to the type prefix if API or client breaking change
- [x] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting))
- [x] 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
- [x] reviewed "Files changed" and left comments if necessary
- [x] 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)

(cherry picked from commit b7097c3)

# Conflicts:
#	CHANGELOG.md
#	x/group/keeper/keeper.go
JeancarloBarrios pushed a commit to agoric-labs/cosmos-sdk that referenced this pull request Sep 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A:automerge Automatically merge PR once all prerequisites pass. C:CLI C:x/auth C:x/authz C:x/group C:x/nft
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants