rs-stellar-xdr
rs-stellar-xdr copied to clipboard
stellar
Rust lib for Stellar XDR.
### What Tools need to always expect TransactionEvleope at the headings. This makes it easy to go in one direction. ### Why [TODO: Why this change is being made. Include...
### What Update readme and docs with new features, and add CI check to keep it updated. Moved the developer instructions into another file. ### Why The readme got out...
### What Add JavaScript bindings via Wasm ### Why Based on #347 and continuation of #351 by @willemneal. The Rust XDR lib is the only implementation of the XDRJSON format....
For example: ``` $ echo -n 'AAAACgAAAAAAAAAAAAAAAAAAAAE=' | stellar-xdr d --type ScVal {"i128":{"hi":0,"lo":1}} ``` That is not very ergonomic to work with. Instead, we could render it as: ``` $...
### What problem does your feature solve? When the CLI is able to guess the type, it's unnecessary to ask the user to provide the type which is more typing....
It would be worthwhile to fuzz the conversion of the Rust types to and from JSON. Most of the types use the derived serde serialization and deserialization, but some types...
It should be possible to encode/decode vararrays of any type, such as doing the equivalent as: ```rust use stellar_xdr::curr::{DepthLimitedRead, DiagnosticEvent, ReadXdr, VecM}; fn main() { let events: VecM = VecM::read_xdr_base64_to_end(&mut...
The tests on the main branch no longer pass because they take 45mins and time out. This doesn't happen on PRs because we speed PRs up by grouping features together...
Blocked by https://github.com/xdrpp/xdrpp/issues/34
It's probably not something we can conveniently do right now. It'll probably be easier to do this once something like https://github.com/stellar/rs-stellar-contract-env/pull/81 is completed.