pezkuwichain/pezkuwi-subxt
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-06-21 07:31:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Initial rebrand from paritytech/subxt to pezkuwichain/pezkuwi-subxt

Browse Source 
- Renamed all subxt crates to pezkuwi-subxt
- Updated internal references
- Configured for Pezkuwi ecosystem
This commit is contained in:
Kurdistan Tech Ministry
2025-12-21 01:46:25 +03:00
commit 99e4ee3ab8
412 changed files with 152913 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testing/test-runtime/README.md
+10
View File
@@ -0,0 +1,10 @@
# 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.