mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-30 06:08:00 +00:00

Files

T

James Wilson 55f04c20a7 Move Subxt crate into a subfolder (#424 )

* move into subfolder step 1

* Make folders a workspace again

* Move examples into their own workspace crate to make them more visible and easier to run

* clippy fix

* newline

* tweak releasing steps for folder move

* reference exampels more clearly in top level readme

2022-02-02 12:15:44 +00:00

src

2022! (#381 )

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

build.rs

Use the generated DispatchError instead of the hardcoded Substrate one (#394 )

2022-01-20 16:35:42 +00:00

Cargo.toml

Move Subxt crate into a subfolder (#424 )

2022-02-02 12:15:44 +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.