Skip to content
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

Complete feature std-fs-io in casper-client feat-2.0 #153

Open
wants to merge 134 commits into
base: feat-track-node-2.0
Choose a base branch
from

Conversation

gRoussac
Copy link
Contributor

@gRoussac gRoussac commented May 6, 2024

Add wasm32-unknown-unknown target

Add default fetaure

Add std-fs-io

cargo build --lib --target wasm32-unknown-unknown --no-default-features

Remove filesystem I/O functionality from the std feature, and gate this behind a new feature std-fs-io which depends upon std.

Allows to compile types without secret_key_from_file/read_transaction_file/make_transaction/send_transaction_file/speculative_send_transaction_file/sign_transaction_file/json_pretty_print/....

Update crates

Add with_bytes() / session_bytes to SessionStrParams payment_bytestoPaymentStrParams`

Pub struct JsonArg

Mutualize code for get_maybe_secret_key()

Add lint-no-default-features/check-no-default-features/keygen::run

Add documentation on args_from_simple_or_json

Add some Clone on exposed result types

Change tokio to [tokio::main(flavor = "current_thread")] as dev branch (required)

@gRoussac
Copy link
Contributor Author

@jacek-casper I believe there is no CI/CD running on feat-track-2.0 branch and that we sould probably add it in

https://github.com/casper-ecosystem/casper-client-rs/blob/rustSDK-feat-2.0/.github/workflows/ci-casper-client-rs.yml#L11

for this branch for PR because it seems to me the branch might not pass cargo audit and clippy

@jacek-casper
Copy link
Contributor

You're right @gRoussac , the CI is not enabled here, it might be worth adding the branch to the workflow file:
https://github.com/casper-ecosystem/casper-client-rs/blob/feat-track-node-2.0/.github/workflows/ci-casper-client-rs.yml#L11

Copy link
Contributor

@jacek-casper jacek-casper left a comment

Choose a reason for hiding this comment

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

lgtm to me, but I think it'd be good to get 1 more approval from someone else familiar with the client

@gRoussac
Copy link
Contributor Author

@jacek-casper You review was great thanks again, I need the PR on node to be merged first and then I will imply Rafal for this one two before merging.

@gRoussac
Copy link
Contributor Author

These PR needs to be backported on feat-track-2.0 and CI/CD implemented on branch

#149
#175

Copy link
Contributor

@rafal-ch rafal-ch left a comment

Choose a reason for hiding this comment

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

LGTM 👍
with just a few nits worth double checking

lib/cli/transaction.rs Outdated Show resolved Hide resolved
lib/cli/transaction.rs Outdated Show resolved Hide resolved
lib/cli/error.rs Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

std-fs-io in casper-client feat-2.0 / dev
4 participants