Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: refactor ICQ module documentation [NTRN-349] #646

Merged
merged 16 commits into from
Nov 29, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
improve wording in MessageKVQueryResult
sotnikov-s committed Nov 29, 2024
commit dd24540bd7c9de3c1e2c8091f7e6dd5eb07c7a71
7 changes: 4 additions & 3 deletions x/contractmanager/types/sudo.go
Original file line number Diff line number Diff line change
@@ -23,9 +23,10 @@ type MessageTxQueryResult struct {

// MessageKvQueryResult is the model of the `sudo` message sent to a smart contract when a KV
// Interchain Query result is submitted. If the owner of a KV Interchain Query wants to handle
// updates, they must implement a `sudo` entry point to process `kv_query_result` messages and
// include the necessary logic in it. The `kv_query_result` handler acts as a callback, triggered
// by the interchainqueries module whenever a KV query result is submitted.
// query updates as part of the result submission transaction, they must implement a `sudo` entry
// point to process `kv_query_result` messages and include the necessary logic in it. The
// `kv_query_result` handler acts as a callback, triggered by the interchainqueries module whenever
// a KV query result is submitted.
//
// Note that the message does not include the actual query result, only the query ID. To access the
// result data, use the `Query/QueryResult` RPC of the `interchainqueries` module.