pezkuwi-subxt

mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-26 13:27:57 +00:00

Files

T

Bastian Köcher d1b0ef76a8 sp-api: Use macro to detect if frame-metadata is enabled (#4117 )

While `sp-api-proc-macro` isn't used directly and thus, it should have
the same features enabled as `sp-api`. However, I have seen issues
around `frame-metadata` not being enabled for `sp-api`, but for
`sp-api-proc-macro`. This can be prevented by using the
`frame_metadata_enabled` macro from `sp-api` that ensures we have the
same feature set between both crates.

2024-04-15 08:11:51 +00:00

proc-macro

sp-api: Use macro to detect if frame-metadata is enabled (#4117 )

2024-04-15 08:11:51 +00:00

src

sp-api: Use macro to detect if frame-metadata is enabled (#4117 )

2024-04-15 08:11:51 +00:00

test

Align dependencies with parity-bridges-common (#3937 )

2024-04-02 13:41:01 +00:00

Cargo.toml

sp-api: Use macro to detect if frame-metadata is enabled (#4117 )

2024-04-15 08:11:51 +00:00

README.md

Markdown linter (#1309 )

2023-09-04 12:02:32 +03:00

README.md

Substrate runtime api

The Substrate runtime api is the crucial interface between the node and the runtime. Every call that goes into the runtime is done with a runtime api. The runtime apis are not fixed. Every Substrate user can define its own apis with decl_runtime_apis and implement them in the runtime with impl_runtime_apis.

Every Substrate runtime needs to implement the [Core] runtime api. This api provides the basic functionality that every runtime needs to export.

Besides the macros and the [Core] runtime api, this crates provides the [Metadata] runtime api, the [ApiExt] trait, the [CallApiAt] trait and the [ConstructRuntimeApi] trait.

On a meta level this implies, the client calls the generated API from the client perspective.

License: Apache-2.0