-
Notifications
You must be signed in to change notification settings - Fork 160
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
Check pause flow #285
Check pause flow #285
Conversation
PR looks good. Only wondering why all those commits are showing up in the PR. @satyamakgec |
contracts/SecurityTokenRegistry.sol
Outdated
@@ -116,10 +116,15 @@ contract SecurityTokenRegistry is ISecurityTokenRegistry, EternalStorage { | |||
* @notice Modifier to make a function callable only when the contract is not paused. | |||
*/ | |||
modifier whenNotPaused() { |
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.
Can you rename to something like whenNotPausedOrOwner - whenNotPaused
might be a bit confusing as it's a standard function with a different normal implementation.
contracts/ModuleRegistry.sol
Outdated
@@ -296,7 +300,7 @@ contract ModuleRegistry is IModuleRegistry, EternalStorage { | |||
/** | |||
* @notice Called by the owner to pause, triggers stopped state | |||
*/ | |||
function pause() external whenNotPaused onlyOwner { | |||
function pause() external onlyOwner { |
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 pause
should revert if the contract is already paused. It makes the logs easier to interpret. Can we have whenNotPaused
and whenNotPausedOrOwner
and use whenNotPaused
here maybe?
@pabloruiz55 the cause of showing all other commits was |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
(Bug fix, feature, docs update, ...)
What is the current behavior?
(You can also link to an open issue here)
Merge only when the
upgrade-mr
PR get merge as I take that upgrade-mr as a base branchWhat is the new behavior?
(Define and describe any new functionality. Clarify if this is a feature change)
Does this PR introduce a breaking change?
(What changes might users need to make in their application due to this PR?)
Any Other information: