James Wilson
72ac18491c
* WIP integrate unstable v16 metadata into Subxt * first pass moving retain to the CLI tool * Remove otuer enum variant stripping and move now simpler strip_metadata to new crate. test it * tidyup to use stripmetadata package etc * Fix / comment out tests * fmt * clippy * Fix wasm example * wasm-example fix * wasm-example fix * Maske sure to move IDs around after types.retain() * fmt * Tweak comment * Find dispatch error separately to avoid issues during mapping * Expose associated type information in pallet metadata * Hopefully fix flaky archive RPC * remove unwanted temp file * Address nits * Add back commented-otu tests and address review comments * use either, and simplify for_each
wasm-example
This is a small WASM app using the Yew UI framework to showcase how to use Subxt's features in a WASM environment.
To run the app locally we first install Trunk, a WASM bundler:
cargo install --locked trunk
You need to have a local polkadot/substrate node with it's JSON-RPC HTTP server running at 127.0.0.1:9933 in order for the examples to be working.
If you have a polkadot binary already, running this should be sufficient:
polkadot --dev
Then, in another terminal, run the app locally with:
trunk serve --open
signing example
For the signing example, we use the @polkadot/extension-dapp NPM package to talk to wallets loaded as browser extensions. In order to sign and submit the transaction using the polkadot --dev node we spawned above, you'll need to create a dev account in your wallet of choice. Use the recovery phrase bottom drive obey lake curtain smoke basket hold race lonely fit walk and the derivation path //Alice to create a dev account that can be used.