mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-25 14:07:58 +00:00

Files

T

Niklas Adolfsson 14e8e6f6b6 add wasm support (#700 )

* get started

* make it work again

* make it compile again

* Use async-wasm-feature of jsonrpsee from the master branch

* Ensure we enable JS feature of getrandom for the wasm target

* Update subxt/src/lib.rs

* update jsonrpsee

* fix CI

* cargo fmt

* fix wasm test

* fix grumbles

* exclude wasm-tests from workspace

To avoid leaking `jsonrpsee-web` feature into the workspace

Co-authored-by: Igor Matuszewski <xanewok@gmail.com>

2022-11-14 11:45:21 +00:00

src

dual license (#590 )

2022-06-28 14:09:41 +01:00

build.rs

add wasm support (#700 )

2022-11-14 11:45:21 +00:00

Cargo.toml

add wasm support (#700 )

2022-11-14 11:45:21 +00:00

README.md

Move test crates into a "testing" folder and add a ui (trybuild) test and ui-test helpers (#567 )

2022-06-17 14:33:58 +01:00

README.md

test-runtime

The logic for this crate exists mainly in the build.rs file.

At compile time, this crate will:

Spin up a local substrate binary (set the SUBSTRATE_NODE_PATH env var to point to a custom binary, otherwise it'll look for substrate on your PATH).
Obtain metadata from this node.
Export the metadata and a node_runtime module which has been annotated using the subxt proc macro and is based off the above metadata.

The reason for doing this is that our integration tests (which also spin up a Substrate node) can then use the generated subxt types from the exact node being tested against, so that we don't have to worry about metadata getting out of sync with the binary under test.