Add sandbox command to contain deploy, invoke, read #144
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.
What
Add sandbox command to contain the sandbox versions of deploy, invoke, read.
Why
I took a quick look at how a remote deploy command would be added (#41) and it soon became overwhelming thinking about how to have such a command coexist with the code in the sandbox deploy command.
At some point someone had expressed interest in grouping sandbox command under a sandbox super command so as to clearly separate them from commands that invoke remote services. I think it might have been @paulbellamy who had dropped this idea in a doc a long time ago.
We never did it, but I think it will make it easier to implement the following tasks if we have the sandbox variations under
sandbox
and put the remote variations of the commands under another subcommand such asremote
:This change makes no functional changes and is purely moving code into a directory (so it is in a Rust module under sandbox), and inserting the sandbox command in between them.
Close #165