mirror of
https://gitlab.com/pezkuwichain/pezkuwi-sdk.git
synced 2026-10-22 03:36:23 +00:00
Kurdistan Tech Ministry
3208f208c0
## Changes
### Clippy Fixes
- Fixed deprecated `cargo_bin` usage in 27 test files (added #![allow(deprecated)])
- Fixed uninlined_format_args in zombienet-sdk-tests
- Fixed subxt API changes in revive/rpc/tests.rs (fetch signature, StorageValue)
- Fixed dead_code warnings in validator-pool and identity-kyc mocks
- Fixed field name `i` -> `_i` in tasks example
### CI Infrastructure
- Added .claude/WORKFLOW_PLAN.md for tracking CI fix progress
- Updated lychee.toml and taplo.toml configs
### Files Modified
- 27 test files with deprecated cargo_bin fix
- bizinikiwi/pezframe/revive/rpc/src/tests.rs (subxt API)
- pezkuwi/pezpallets/validator-pool/src/{mock,tests}.rs
- pezcumulus/teyrchains/pezpallets/identity-kyc/src/mock.rs
- bizinikiwi/pezframe/examples/tasks/src/tests.rs
## Status
- cargo clippy: PASSING
- Next: cargo fmt, zepter, workspace checks
26 lines
1.3 KiB
Rust
26 lines
1.3 KiB
Rust
//! # Metadata
|
|
//!
|
|
//! The existence of metadata in pezkuwi-sdk goes back to the (forkless) upgrade-ability of all
|
|
//! Bizinikiwi-based blockchains, which is achieved through
|
|
//! [`crate::reference_docs::wasm_meta_protocol`]. You can learn more about the details of how to
|
|
//! deal with these upgrades in [`crate::reference_docs::frame_runtime_upgrades_and_migrations`].
|
|
//!
|
|
//! Another consequence of upgrade-ability is that as a UI, wallet, or generally an offchain entity,
|
|
//! it is hard to know the types internal to the runtime, specifically in light of the fact that
|
|
//! they can change at any point in time.
|
|
//!
|
|
//! This is why all Bizinikiwi-based runtimes must expose a [`pezsp_api::Metadata`] api, which
|
|
//! mandates the runtime to return a description of itself. The return type of this api is
|
|
//! `Vec<u8>`, meaning that it is up to the runtime developer to decide on the format of this.
|
|
//!
|
|
//! All [`crate::pezkuwi_sdk::frame_runtime`] based runtimes expose a specific metadata language,
|
|
//! maintained in <https://github.com/paritytech/frame-metadata> which is adopted in the Pezkuwi
|
|
//! ecosystem.
|
|
//!
|
|
//! ## Metadata Explorers:
|
|
//!
|
|
//! A few noteworthy tools that inspect the (FRAME-based) metadata of a chain:
|
|
//!
|
|
//! - <https://wiki.network.pezkuwichain.io/docs/metadata>
|
|
//! - <https://paritytech.github.io/subxt-explorer/>
|