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.
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: ctrl port connection id validation #454
chore: ctrl port connection id validation #454
Changes from 19 commits
755ce69
a8128ce
bce3407
cd8ac79
45d8f8d
1ec19f1
5d01500
0c56d06
d3039bb
6761d2d
e22f3ea
09f741a
6982141
88bc3c8
31536af
d09703e
ac87f9d
b6925ab
c21c153
a8bab3a
6cedcf1
59340ac
c84996f
495c864
f68d7ec
b4d1191
9d4dfd7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
maybe the error message should say connection params? Otherwise maybe we should rename the function to
validateControllerPort
?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.
Sure thing! Any preference on this before I update?
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.
I think
validateControllerPort
makes the most sense to me. It will likely align closer with the ICS specThere 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.
Cool, I've updated to
validateControllerPort
. My only gripe with this, and perhaps its overly pedantic, is that we never actually pass the controller port to this function. We pass the self port ID to retrieve the channel which is obviously going to be different in theOnChainOpenInit
andOnChanOpenTry
callbacks.We could... 🤔
validateControllerPortParams
and leave the args the same.The only problem I see with opt 2 is that having two port ID args may be confusing(?), while opt 1 is a bit long winded...
Either way I'm happy to leave it as is now if you are 😄
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.
I vote for
validateControllerPortParams and leave the args the same
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.
Format string here may look a little odd using
%[1]s
, see explicit argument indexing here. Avoids having to specifytypes.Delimiter
multiple times in args.Suggestions for a better error message are welcome, but I think including the expected format as @crodriguezvega mentioned would be valuable.
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.
I'd define the expected string as a const and then link the spec in the comment for the expected format. I'd also recommend using
controller-conn-seq
andhost-conn-seq
since counterparty means different things depending on context