mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-27 17:28:00 +00:00

Files

T

Andrew Jones 11f24d78f7 Update scale-info and parity-scale-codec requirements (#462 )

* Update scale-info and parity-scale-codec requirements

* Update CHANGELOG

* Update frame-metadata

* Update bitvec

* Fix test

* Update bitvec event decoding

* More bitvec updates

* Update substrate primitives dependencies

* Fix up bitvec errors and decode error

* Fix up bitvec errors

* Update polkadot codegen

2022-03-01 16:36:38 +00:00

src

2022! (#381 )

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

build.rs

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

2022-02-04 10:46:39 +00:00

Cargo.toml

Update scale-info and parity-scale-codec requirements (#462 )

2022-03-01 16:36:38 +00: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.