mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-24 15:57:58 +00:00

Files

T

Andrew Jones 389f20ff94 Update substrate crates (#709 )

* Patch all substrate deps to use my substrate branch

* default-features = false causing issus in test-runtime

* Use substrate polkadot release branch

* Use default-features for sp-runtime again :(

* Restore default-features for subxt-cli/sp-core

* Fix module error integration test

* Add Send + Sync bounds to ExtrinsicEvents::iter()

* Elide lifetime

* Revert adding Send + Sync

* Add Sync bound to Rpc::ClientError

* Remove version in subxt-metadata

* Use released crates

* Use released sp-keyring

* Fix sp-keyring deps

* Remove unnecessary sp-keyring default-features = false

2022-11-16 13:21:17 +01: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

Update substrate crates (#709 )

2022-11-16 13:21:17 +01: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.