Change counterpartyInfo to channel #100
Open
+166
−137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR renames
counterpartyInfo
tochannel
Moreover it does not assume that the counterpartyId is necessarily a clientID. I think here the logic looks much more in-line with IBC-go and hopefully will do a lot to remove the confusions raised in the referenced spec issue.
For now, I have a single contract implementing ICS02 and ICS04 specs since ICS04 doesn't have too many additional functions. I can rename the file to
CoreRouter
to make this clearer rather than ICS02Client.TODO:
ref: cosmos/ibc#1164
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.
godoc
comments.Files changed
in the GitHub PR explorer.SonarCloud Report
in the comment section below once CI passes.