mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-05-31 14:31:02 +00:00
Use same fmt and clippy configs as in Substrate (#7611)
* Use same rustfmt.toml as Substrate Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * format format file Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Format with new config Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Add Substrate Clippy config Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Print Clippy version in CI Otherwise its difficult to reproduce locally. Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Make fmt happy Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Update node/core/pvf/src/error.rs Co-authored-by: Tsvetomir Dimitrov <tsvetomir@parity.io> * Update node/core/pvf/src/error.rs Co-authored-by: Tsvetomir Dimitrov <tsvetomir@parity.io> --------- Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> Co-authored-by: Tsvetomir Dimitrov <tsvetomir@parity.io>
This commit is contained in:
committed by
GitHub
parent
ac435c96cf
commit
342d720573
@@ -287,13 +287,13 @@ impl IsSystem for Sibling {
|
||||
}
|
||||
}
|
||||
|
||||
/// A type that uniquely identifies an HRMP channel. An HRMP channel is established between two paras.
|
||||
/// In text, we use the notation `(A, B)` to specify a channel between A and B. The channels are
|
||||
/// unidirectional, meaning that `(A, B)` and `(B, A)` refer to different channels. The convention is
|
||||
/// that we use the first item tuple for the sender and the second for the recipient. Only one channel
|
||||
/// is allowed between two participants in one direction, i.e. there cannot be 2 different channels
|
||||
/// identified by `(A, B)`. A channel with the same para id in sender and recipient is invalid. That
|
||||
/// is, however, not enforced.
|
||||
/// A type that uniquely identifies an HRMP channel. An HRMP channel is established between two
|
||||
/// paras. In text, we use the notation `(A, B)` to specify a channel between A and B. The channels
|
||||
/// are unidirectional, meaning that `(A, B)` and `(B, A)` refer to different channels. The
|
||||
/// convention is that we use the first item tuple for the sender and the second for the recipient.
|
||||
/// Only one channel is allowed between two participants in one direction, i.e. there cannot be 2
|
||||
/// different channels identified by `(A, B)`. A channel with the same para id in sender and
|
||||
/// recipient is invalid. That is, however, not enforced.
|
||||
#[derive(Clone, PartialEq, Eq, PartialOrd, Ord, Encode, Decode, RuntimeDebug, TypeInfo)]
|
||||
#[cfg_attr(feature = "std", derive(Hash))]
|
||||
pub struct HrmpChannelId {
|
||||
@@ -414,6 +414,7 @@ pub struct ValidationResult {
|
||||
///
|
||||
/// It is expected that the Parachain processes them from first to last.
|
||||
pub processed_downward_messages: u32,
|
||||
/// The mark which specifies the block number up to which all inbound HRMP messages are processed.
|
||||
/// The mark which specifies the block number up to which all inbound HRMP messages are
|
||||
/// processed.
|
||||
pub hrmp_watermark: RelayChainBlockNumber,
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user