-
Notifications
You must be signed in to change notification settings - Fork 98
Add support for vector<vector> #3398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Can you add a sample entry function in and call the function in rooch/crates/testsuite/features/cmd.feature Lines 237 to 268 in cc64247
|
I've made these changes. Do they look good to you? |
@@ -263,6 +263,8 @@ Feature: Rooch CLI integration tests | |||
Then assert: "{{$.move[-1].execution_info.status.type}} == executed" | |||
Then cmd: "move run --function default::entry_function::emit_object_mut --args "object:default::entry_function::TestStruct" --json" | |||
Then assert: "{{$.move[-1].execution_info.status.type}} == executed" | |||
Then cmd: "move run --function default::entry_function::emit_vec_vec_u8 --args "vector<vector<u8>>:std::vector[2,3,4],std::vector[5,6,7]" --json" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a valid format?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests failed due to this. I'm looking into it.
Summary
This PR adds support to pass vector as transaction arguments. Please let me know if these changes look good and whether I should constrain the concrete type of inner vector to u8.
[cli] Support pass vector<vector<u8>> as transaction arguments #3294