-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Rename InfoImporter -> LegacyInfoImporter #8739
Conversation
Avoid namespace clash with the InfoImporter interface that already exists in the v0.41 release series.
Codecov Report
@@ Coverage Diff @@
## master #8739 +/- ##
=======================================
Coverage 61.44% 61.44%
=======================================
Files 673 673
Lines 38361 38361
=======================================
Hits 23571 23571
Misses 12309 12309
Partials 2481 2481
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving, but could you explain the motivation? There is no other InfoImporter
. As you wrote in the description there was one in the past, but it's not clear what's the problem with keeping the same name?
@robert-zaremba there is one InfoImporter interface in the keyring package of 0.41. The interfaces' methods are different |
Avoid namespace clash with the InfoImporter interface that already exists in the v0.41 release series. (cherry picked from commit 010eeef) # Conflicts: # client/keys/migrate.go # crypto/keyring/keyring.go
Ah, I was looking at master :palm_face: |
Avoid namespace clash with the InfoImporter interface that already exists in the v0.41 release series.
* crypto/keyring: fix offline keys migration (#8639) Fix `keys migrate` command (#8703) crypto/keyring: reinstate the InfoImporter interface InfoImporter is implemented by those Keyring implementations that support import of Info objects. Co-authored-by: Alessio Treglia <alessio@tendermint.com> Co-authored-by: Jonathan Gimeno <jgimeno@gmail.com> Co-authored-by: Amaury <1293565+amaurym@users.noreply.github.com> * refresh golangci-lint * Rename InfoImporter -> LegacyInfoImporter (#8739) Avoid namespace clash with the InfoImporter interface that already exists in the v0.41 release series. * Revert "refresh golangci-lint" This reverts commit 38e1349. Co-authored-by: SaReN <sahithnarahari@gmail.com> Co-authored-by: Jonathan Gimeno <jgimeno@gmail.com> Co-authored-by: Amaury <1293565+amaurym@users.noreply.github.com>
Avoid namespace clash with the InfoImporter interface
that already exists in the v0.41 release series.
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerCodecov Report
in the comment section below once CI passes