chore: regenerate umbrella crate, fix feature propagation
This commit is contained in:
@@ -17,12 +17,12 @@
|
||||
|
||||
//! Bizinikiwi runtime api
|
||||
//!
|
||||
//! The Bizinikiwi runtime api is the interface between the node and the runtime. There isn't a fixed
|
||||
//! set of runtime apis, instead it is up to the user to declare and implement these runtime apis.
|
||||
//! The declaration of a runtime api is normally done outside of a runtime, while the implementation
|
||||
//! of it has to be done in the runtime. We provide the [`decl_runtime_apis!`] macro for declaring
|
||||
//! a runtime api and the [`impl_runtime_apis!`] for implementing them. The macro docs provide more
|
||||
//! information on how to use them and what kind of attributes we support.
|
||||
//! The Bizinikiwi runtime api is the interface between the node and the runtime. There isn't a
|
||||
//! fixed set of runtime apis, instead it is up to the user to declare and implement these runtime
|
||||
//! apis. The declaration of a runtime api is normally done outside of a runtime, while the
|
||||
//! implementation of it has to be done in the runtime. We provide the [`decl_runtime_apis!`] macro
|
||||
//! for declaring a runtime api and the [`impl_runtime_apis!`] for implementing them. The macro docs
|
||||
//! provide more information on how to use them and what kind of attributes we support.
|
||||
//!
|
||||
//! It is required that each runtime implements at least the [`Core`] runtime api. This runtime api
|
||||
//! provides all the core functions that Bizinikiwi expects from a runtime.
|
||||
@@ -95,7 +95,6 @@ pub mod __private {
|
||||
pub use alloc::vec;
|
||||
pub use codec::{self, Decode, DecodeLimit, Encode};
|
||||
pub use core::{mem, slice};
|
||||
pub use scale_info;
|
||||
pub use pezsp_core::offchain;
|
||||
#[cfg(not(feature = "std"))]
|
||||
pub use pezsp_core::to_bizinikiwi_wasm_fn_return_value;
|
||||
@@ -108,6 +107,7 @@ pub mod __private {
|
||||
ExtrinsicInclusionMode, TransactionOutcome,
|
||||
};
|
||||
pub use pezsp_version::{create_apis_vec, ApiId, ApisVec, RuntimeVersion};
|
||||
pub use scale_info;
|
||||
|
||||
#[cfg(all(any(target_arch = "riscv32", target_arch = "riscv64"), bizinikiwi_runtime))]
|
||||
pub use pezsp_runtime_interface::polkavm::{polkavm_abi, polkavm_export};
|
||||
@@ -395,9 +395,9 @@ pub use pezsp_api_proc_macro::decl_runtime_apis;
|
||||
/// [`decl_runtime_apis!`] declares two version of the api - 1 (the default one, which is
|
||||
/// considered stable in our example) and 99 (which is considered staging). In
|
||||
/// `impl_runtime_apis!` a `cfg_attr` attribute is attached to the `ApiWithStagingMethod`
|
||||
/// implementation. If the code is compiled with `enable-pezstaging-api` feature a version 99 of
|
||||
/// the runtime api will be built which will include `pezstaging_one`. Note that `pezstaging_one`
|
||||
/// implementation is feature gated by `#[cfg(feature = ... )]` attribute.
|
||||
/// implementation. If the code is compiled with `enable-pezstaging-api` feature a version 99
|
||||
/// of the runtime api will be built which will include `pezstaging_one`. Note that
|
||||
/// `pezstaging_one` implementation is feature gated by `#[cfg(feature = ... )]` attribute.
|
||||
///
|
||||
/// If the code is compiled without `enable-pezstaging-api` version 1 (the default one) will be
|
||||
/// built which doesn't include `pezstaging_one`.
|
||||
|
||||
Reference in New Issue
Block a user