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

Files

T

History

pezkuwichain b8ee6a084f Rebrand subxt to pezkuwi-subxt with pezsp_runtime support

- Renamed all crate names from subxt-* to pezkuwi-subxt-*
- Updated codegen to use pezsp_runtime, pezsp_core, pezframe_support instead of sp_runtime, sp_core, frame_support
- Replaced all internal references from subxt_* to pezkuwi_subxt_*
- Added local path dependencies to Pezkuwi SDK crates
- Updated workspace configuration for edition 2024

2025-12-19 16:00:14 +03:00

src

Metadata V16: Implement support for Pallet View Functions (#1981 )

2025-04-24 14:42:07 +01:00

build.rs

Support v16 metadata and use it by default if it's available (#1999 )

2025-05-08 14:44:44 +01:00

Cargo.toml

Rebrand subxt to pezkuwi-subxt with pezsp_runtime support

2025-12-19 16:00:14 +03:00

README.md

Move test crates into a "testing" folder and add a ui (trybuild) test and ui-test helpers (#567 )

2022-06-17 14:33:58 +01: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.