Disable Token Actions if Not Available #2326
Merged
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.
Intro Note
This PR is part of the set that will be opened by me to (re)introduce all the changes made to support the Arbitrum deployment, from the
master-arbitrum
branch back intomaster
so that the two branches can be (more or less) identicalWe need to run two branches, since AWS enforces one deployment per branch, meaning we can't run both the
Gnosis
andArbitrum
deployment from the same branch.This will get cleaned up, once we get to Multichain and we will be back to only supporting one main deployment (which itself will support multiple networks, whatever form this might take)
Current PR Details
This PR adds some checks to disable the "Mint Token" and "Unlock Token" actions if the colony doesn't have permissions to do so. This usually happens when you are using an external token, not one created by you, when creating the colony.
Testing
Testing this is quite easy, just create a new colony, but instead of creating a new token along side it, just bring one from an existing colony (
planex
for example).Resolves #2163