refactor(stellar): reorganize deploy-contract command structure #544
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
npty
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
https://axelarnetwork.atlassian.net/browse/AXE-7489
This PR refactors
stellar/deploy-contract.jsscript to allow passing contract specific options for thedeploycommand, follow the same pattern in sui.I've also refactored the
--use-dummy-its-addressoption intoexamplecontract config as I assumed that it is used with example contract deployment here. While theexamplecontract is not currently included in theSUPPORTED_CONTRACTconstant, this refactoring prepares the configuration structure for its future integration. Let me know if this is incorrect assumption.Impact
This changes doesn't affect the
deploymentorupgradeinstructions mentioned in theREADME.mdfile.