-
Notifications
You must be signed in to change notification settings - Fork 112
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
Feat/multichain reputation rebased hardhat 2 #1238
Conversation
…n-reputation-rebased-hardhat-2
I've included your suggested changes to the migrations, though really they should have been deleted in #1196 😄 |
6cb7ac0
to
dd974be
Compare
dd974be
to
15c78f3
Compare
|
||
bool success = callThroughBridgeWithGuards(payload); | ||
|
||
if (success) { |
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.
Could do this as
require(success, "colony-network-bridging-tx-unsuccessful");
emit ReputationUpdateSentToBridge(_colony, _updateNumber);
); | ||
return skill.children[_childSkillIndex]; | ||
return; |
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.
Why not do an else
here?
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.
This is the same pattern as came up recently, namely that I don't want to forget that we introduced the else
to implicitly mean 'and do nothing else in the if branch', and then introduce something after the if
statement at a later date that breaks that assumption.
8a1a142
to
0d9436c
Compare
Intended to be the same as #1216 but based on #1196. #1237 is based on this branch.