mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-22 11:27:58 +00:00

Files

T

Andrew Jones cc0f980d95 Use released substrate dependencies (#375 )

* WIP update dependencies to crates versions

* Use released versions of sp-version and sp-arithmetic

* Attempt to align version of sp-keyring used to correspond to 4.0.0 releases. No luck but closer

* sp-keyring 4.0.0

* also sp-keyring 4.0.0 for macro crate

* simplify cargo.tomls

Co-authored-by: James Wilson <james@jsdw.me>

2022-01-17 14:25:15 +00:00

src

2022! (#381 )

2022-01-05 10:26:03 +00:00

build.rs

2022! (#381 )

2022-01-05 10:26:03 +00:00

Cargo.toml

Use released substrate dependencies (#375 )

2022-01-17 14:25:15 +00:00

README.md

Ensure metadata is in sync with running node during tests (#333 )

2021-11-29 09:39:40 +00: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, otehrwise 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.