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

Files

T

James Wilson dffeee431e Release prep for 0.20.0 (#502 )

* v0.20.0 release prep

* wee text tweak

* remove dry-run step that doesn't actually work

* Fix typo

Co-authored-by: Alexandru Vasile <60601340+lexnv@users.noreply.github.com>

* No more "in"

Co-authored-by: Tarik Gul <47201679+TarikGul@users.noreply.github.com>

* Fix "customized" typo

Co-authored-by: Tarik Gul <47201679+TarikGul@users.noreply.github.com>

Co-authored-by: Alexandru Vasile <60601340+lexnv@users.noreply.github.com>
Co-authored-by: Tarik Gul <47201679+TarikGul@users.noreply.github.com>

2022-04-06 16:42:10 +01:00

src

2022! (#381 )

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

build.rs

Rely on the kernel for port allocation (#498 )

2022-04-05 20:57:02 +03:00

Cargo.toml

Release prep for 0.20.0 (#502 )

2022-04-06 16:42:10 +01:00

README.md

Add more tests for events.rs/decode_and_consume_type (#430 )

2022-02-04 10:46:39 +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, 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.