mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-22 19:38:00 +00:00

Files

T

James Wilson 643795919f Use the generated DispatchError instead of the hardcoded Substrate one (#394 )

* WIP DispatchError generic param

* main crate now compiling with new E generic param for DispatchError

* Remove E param from RpcClient since it doesn't really need it

* Point to generated DispatchError in codegen so no need for additional param there

* More error hunting; cargo check --all-targets passes now

* Use our own RuntimeVersion struct (for now) to avoid error decoding into sp_version::RuntimeVersion

* cargo fmt

* fix docs and expose private documented thing that I think should be pub

* move error info to compile time so that we can make DispatchError a little nicer to work with

* cargo fmt

* clippy

* Rework error handling to remove <E> param in most cases

* fix Error doc ambiguity (hopefully)

* doc tweaks

* docs: remove dismbiguation thing that isn't needed now

* One more Error<E> that can be a BasicError

* rewrite pallet errors thing into normal loops to tidy

* tidy errors codegen a little

* tidy examples/custom_type_derives.rs a little

* cargo fmt

* silcnce clippy in example

2022-01-20 16:35:42 +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

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.