Change upgrade_client_proposal_handler -> `execute_upgrade_client_p…

…roposal`

ibc-core/ics02-client/types/src/msgs/recover_client.rs

@@ -13,7 +13,11 @@ pub const RECOVER_CLIENT_TYPE_URL: &str = "/ibc.core.client.v1.MsgRecoverClient"
 /// Defines the message used to recover a frozen or expired client.
 ///
 /// Note that a frozen or expired client can only be recovered by passing
-/// a governance proposal.
+/// a governance proposal. For this reason, ibc-rs does not export dispatching
+/// a `MsgRecoverClient` via the `dispatch` function. In other words, the
+/// client recovery functionality is not part of ibc-rs's public API. The
+/// intended usage of this message type is to be integrated with hosts'
+/// governance modules, not to be called directly via `dispatch`.
 #[cfg_attr(
     feature = "borsh",
     derive(borsh::BorshSerialize, borsh::BorshDeserialize)

ibc-core/ics24-host/cosmos/src/upgrade_proposal/handler.rs

@@ -7,12 +7,12 @@ use tendermint::abci::Event as TmEvent;
 use super::UpgradedClientStateRef;
 use crate::upgrade_proposal::{UpgradeClientProposal, UpgradeExecutionContext, UpgradeProposal};
 
-/// Handles an upgrade client proposal
+/// Executes an upgrade client proposal.
 ///
 /// It clears both IBC client and consensus states if a previous plan was set.
 /// Then it will schedule an upgrade and finally set the upgraded client state
 /// in upgrade store.
-pub fn upgrade_client_proposal_handler<Ctx>(
+pub fn execute_upgrade_client_proposal<Ctx>(
     ctx: &mut Ctx,
     proposal: UpgradeProposal,
 ) -> Result<TmEvent, UpgradeClientError>

ibc-core/ics24-host/cosmos/src/upgrade_proposal/mod.rs

@@ -8,6 +8,6 @@ mod proposal;
 
 pub use context::*;
 pub use events::{UpgradeChain, UpgradeClientProposal};
-pub use handler::upgrade_client_proposal_handler;
+pub use handler::execute_upgrade_client_proposal;
 pub use plan::Plan;
 pub use proposal::UpgradeProposal;