-
Notifications
You must be signed in to change notification settings - Fork 72
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
Fix/stellar asset bindings #1332
Fix/stellar asset bindings #1332
Conversation
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.
Just a few nits. Also looks like you have to run cargo fmt
. Good first real Rust PR! 🎉
6d5a5a7
to
7051f3b
Compare
6b8356f
to
859ef53
Compare
@elizabethengelman Any ideas on the failing emulator tests? |
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.
Just two small nits, but otherwise this looks great!
8fb73a9
to
0d4b52e
Compare
It looks like the emulator tests are passing now, but definitely something we should keep an eye on in case they are flakey. |
remove unnecessary public modifier Co-authored-by: Willem Wyndham <willem@wyndham.tech>
prevent cloning Co-authored-by: Willem Wyndham <willem@wyndham.tech>
0d4b52e
to
393e6e4
Compare
What
Bindings command can now generate for a StellarAsset type contract. Fixes #1312
Logic for checking if its a StellarAsset was extracted from
invoke.rs
toget_spec.rs
used by bothinvoke
andbindings
.Why
Bindings were failing when trying to retrieve the wasm for a StellarAsset type from the contract Id.
Known limitations
none