Skip to content

Conversation

@stevencartavia
Copy link
Contributor

Motivation

closes #12987

Solution

PR Checklist

  • Added Tests
  • Added Documentation
  • Breaking changes

Comment on lines 38 to 45
/// Parsed transaction specification
#[derive(Debug, Clone)]
pub struct TxSpec {
pub to: String,
pub value: Option<String>,
pub sig: Option<String>,
pub args: Vec<String>,
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are these parsed differently?

if not we can unify them and avoid duplicating parsing

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unified

///
/// Examples:
/// --tx "0x123:0.1ether" (ETH transfer)
/// --tx "0x456::transfer(address,uint256):0x789,1000" (contract call)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we add some clap test for this, because I believe the signature must be wrapped in a string due to the ,?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated it to ;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Batch sending in cast

2 participants