You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 31, 2020. It is now read-only.
Currently, when you call setCooldown on a button, it resets the cooldown to the new value, even if it's shorter. Would it be preferred to keep the existing cooldown if longer, and perhaps provide an optional boolean argument overwriiteCoolodwn to setCooldown to force replacement of the cooldown?
Depending on your point of view, this could be seen as either a breaking change, or as a bugfix where the intended behavior would be to keep the longer cooldown.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, when you call setCooldown on a button, it resets the cooldown to the new value, even if it's shorter. Would it be preferred to keep the existing cooldown if longer, and perhaps provide an optional boolean argument
overwriiteCoolodwn
tosetCooldown
to force replacement of the cooldown?Depending on your point of view, this could be seen as either a breaking change, or as a bugfix where the intended behavior would be to keep the longer cooldown.
The text was updated successfully, but these errors were encountered: