mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-24 22:57:57 +00:00
Alexandru Vasile
e9be43aaff
* lib: Export `GenericError` to avoid linking to private items Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * Bump version to v0.17.0 Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * doc: Add crates to bump Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * Update changelog Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * changelog: Add new line between title and list Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * releasing: Remove extra closing bracket Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * releasing: Fix cargo install typo for cargo-hack Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * Remove subxt version from macro and test-runtime Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * releasing: Change PR link to sort in descending order Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * changelog: Add missing PR Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
test-runtime
The logic for this crate exists mainly in the build.rs file.
At compile time, this crate will:
- Spin up a local
substratebinary (set theSUBSTRATE_NODE_PATHenv var to point to a custom binary, otherwise it'll look forsubstrateon your PATH). - Obtain metadata from this node.
- Export the metadata and a
node_runtimemodule which has been annotated using thesubxtproc 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.