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

[R4R]: Cleanup bank keeper #2719

Merged
merged 2 commits into from
Nov 12, 2018
Merged

[R4R]: Cleanup bank keeper #2719

merged 2 commits into from
Nov 12, 2018

Conversation

alexanderbez
Copy link
Contributor

The bank keeper was broken up into sub-interfaces (view, send, main). However, we were repeating a bulk of the methods in each. This simply removes duplicate code and DRYs it up.


  • Targeted PR against correct branch (see CONTRIBUTING.md)

  • Linked to github-issue with discussion and accepted design OR link to spec that describes this work.

  • Wrote tests

  • Updated relevant documentation (docs/)

  • Added entries in PENDING.md with issue #

  • rereviewed Files changed in the github PR explorer


For Admin Use:

  • Added appropriate labels to PR (ex. wip, ready-for-review, docs)
  • Reviewers Assigned
  • Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

@alexanderbez alexanderbez added wip Type: Code Hygiene General cleanup and restructuring of code to provide clarity, flexibility, and modularity. labels Nov 7, 2018
@alexanderbez alexanderbez changed the title [WIP]: Cleanup bank keeper [R4R]: Cleanup bank keeper Nov 7, 2018
@codecov
Copy link

codecov bot commented Nov 7, 2018

Codecov Report

Merging #2719 into release/v0.26.0 will decrease coverage by 0.01%.
The diff coverage is 100%.

@@                 Coverage Diff                 @@
##           release/v0.26.0    #2719      +/-   ##
===================================================
- Coverage            57.63%   57.62%   -0.02%     
===================================================
  Files                  154      154              
  Lines                 9570     9563       -7     
===================================================
- Hits                  5516     5511       -5     
+ Misses                3690     3688       -2     
  Partials               364      364

@alexanderbez
Copy link
Contributor Author

alexanderbez commented Nov 7, 2018

@cwgoes mind getting this in (I'd like another approval)?

@sunnya97
Copy link
Member

sunnya97 commented Nov 7, 2018

@alexanderbez Here is the context for why the Keepers are like this. #831 (comment)

x/bank/keeper.go Outdated Show resolved Hide resolved
x/bank/keeper.go Outdated Show resolved Hide resolved
x/bank/keeper.go Show resolved Hide resolved
x/bank/keeper.go Outdated Show resolved Hide resolved
@alexanderbez
Copy link
Contributor Author

@rigelrozanski addressed your comments 👍

@alexanderbez alexanderbez changed the base branch from release/v0.26.0 to develop November 7, 2018 21:43
@cwgoes
Copy link
Contributor

cwgoes commented Nov 8, 2018

@sunnya97 I don't think we have diamond inheritance in this case, so this pattern seems OK.

@alexanderbez
Copy link
Contributor Author

Yea there is no diamond inheritance here afaict.

Copy link
Contributor

@cwgoes cwgoes left a comment

Choose a reason for hiding this comment

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

utACK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Code Hygiene General cleanup and restructuring of code to provide clarity, flexibility, and modularity.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants