Closed aarmoa closed 2 months ago
This update primarily introduces a series of JSON schema files to enhance the documentation and SDK support for various blockchain functionalities, including IBC transfers, Tendermint specifics, and more. It also includes visual improvements like HTML line breaks in Markdown files to ensure better readability across different sections.
File Path | Change Summary |
---|---|
source/includes/_*.md |
Added <br/> tags for visual separation in various sections. |
source/json_tables/chain/ibc/... |
Introduced JSON schemas for IBC core functionalities like channel, client, and transfer specifics. |
source/json_tables/chain/tendermint/... |
Added new JSON schema files defining various aspects of Tendermint blockchain operations. |
source/includes/_changelog.md |
Updated Python SDK support for new queries. |
source/index.html.md |
New entries added for modules in documentation. |
🐰✨ A hop of joy, a leap of code, Changes vast where data flowed. Through blockchain's maze, paths we pave, With schemas new, the docs we save. Celebrate, for progress shows, In every line, where knowledge grows. 🎉
source/json_tables/chain/ibc/core/channel/queryChannelsRequest.json (1)
`1-3`: LGTM! The JSON schema for the channel query request is well-defined and correctly marks pagination as optional.source/json_tables/chain/ibc/core/client/queryUpgradedConsensusStateResponse.json (1)
`2-2`: LGTM! The description for "upgraded_consensus_state" is clear and informative.source/json_tables/chain/ibc/transfer/queryDenomHashRequest.json (1)
`2-2`: LGTM! The description for "trace" is detailed and provides clear context.source/json_tables/chain/tendermint/evidence.json (1)
`2-2`: LGTM! The description for "sum" is clear and specifies the valid types of evidence.source/json_tables/chain/tendermint/getBlockByHeightResponse.json (2)
`2-2`: The definition of "block_id" is clear and correctly typed. --- `3-3`: The definition of "sdk_block" is clear and correctly typed.source/json_tables/chain/tendermint/getLatestBlockResponse.json (2)
`2-2`: The definition of "block_id" is clear and correctly typed. --- `3-3`: The definition of "sdk_block" is clear and correctly typed.source/json_tables/chain/ibc/core/client/identifiedClientState.json (2)
`2-2`: The definition of "client_id" is clear and correctly typed. --- `3-3`: The definition of "client_state" is clear and correctly typed.source/json_tables/chain/ibc/core/client/consensusStateWithHeight.json (2)
`2-2`: The definition of "height" is clear and correctly typed. --- `3-3`: The definition of "consensus_state" is clear and correctly typed.source/json_tables/chain/ibc/transfer/denomTrace.json (2)
`2-2`: The definition of "path" is clear and correctly typed. --- `3-3`: The definition of "base_denom" is clear and correctly typed.source/json_tables/chain/tendermint/defaultNodeInfoOther.json (2)
`2-2`: The definition of "tx_index" is clear and correctly typed. --- `3-3`: The definition of "rpc_address" is clear and correctly typed.source/json_tables/chain/ibc/core/channel/queryUnreceivedAcksResponse.json (2)
`2-2`: The definition of "sequences" is clear and correctly typed. --- `3-3`: The definition of "height" is clear and correctly typed.source/json_tables/chain/ibc/core/channel/queryUnreceivedPacketsResponse.json (1)
`1-4`: The JSON schema is well-defined and correctly specifies the types and descriptions for the parameters. Good job ensuring clarity and accuracy in the documentation.source/json_tables/chain/tendermint/getNodeInfoResponse.json (1)
`1-4`: The JSON schema is well-defined and correctly specifies the types and descriptions for the parameters. Good job ensuring clarity and accuracy in the documentation.source/json_tables/chain/ibc/core/channel/queryNextSequenceReceiveRequest.json (1)
`1-4`: The JSON schema is well-defined and correctly specifies the types, descriptions, and required status for the parameters. Good job ensuring clarity and accuracy in the documentation.source/json_tables/chain/ibc/transfer/queryEscrowAddressRequest.json (1)
`1-4`: The JSON schema is well-defined and correctly specifies the types, descriptions, and required status for the parameters. Good job ensuring clarity and accuracy in the documentation.source/json_tables/chain/tendermint/getValidatorSetByHeightRequest.json (1)
`1-4`: The JSON schema is well-defined and correctly specifies the types, descriptions, and required status for the parameters. Good job ensuring clarity and accuracy in the documentation.source/json_tables/chain/tendermint/module.json (1)
`1-5`: The JSON schema is well-defined and correctly specifies the types and descriptions for the parameters. Good job ensuring clarity and accuracy in the documentation.source/json_tables/chain/ibc/core/height.json (1)
`1-4`: The JSON schema is well-defined and correctly specifies the types and descriptions for the parameters. Good job ensuring clarity and accuracy in the documentation.source/json_tables/chain/ibc/core/client/queryConsensusStateHeightsRequest.json (2)
`2-2`: The definition of the `client_id` parameter is clear and complete. --- `3-3`: The optional `pagination` parameter is appropriately documented.source/json_tables/chain/ibc/core/channel/queryChannelResponse.json (3)
`2-2`: The `channel` parameter is clearly defined. --- `3-3`: The `proof` parameter is appropriately documented. --- `4-4`: The `proof_height` parameter is clearly defined.source/json_tables/chain/ibc/core/channel/queryPacketCommitmentsResponse.json (3)
`2-2`: The `commitments` parameter is clearly defined. --- `3-3`: The `pagination` parameter is appropriately documented. --- `4-4`: The `height` parameter is clearly defined.source/json_tables/chain/ibc/core/client/params.json (1)
`2-2`: The `allowed_clients` parameter is clearly defined and explains the implications of client type changes.source/json_tables/chain/ibc/core/channel/queryPacketReceiptResponse.json (3)
`2-2`: The `received` parameter is clearly defined and appropriately indicates the receipt status. --- `3-3`: The `proof` parameter is appropriately documented. --- `4-4`: The `proof_height` parameter is clearly defined.source/json_tables/chain/ibc/core/channel/queryPacketAcknowledgementRequest.json (3)
`2-2`: The `port_id` parameter is clearly defined and marked as required. --- `3-3`: The `channel_id` parameter is appropriately documented and marked as required. --- `4-4`: The `sequence` parameter is clearly defined and marked as required.source/json_tables/chain/ibc/core/channel/queryPacketReceiptRequest.json (3)
`2-2`: The `port_id` parameter is clearly defined and marked as required. --- `3-3`: The `channel_id` parameter is appropriately documented and marked as required. --- `4-4`: The `sequence` parameter is clearly defined and marked as required.source/json_tables/chain/ibc/core/client/queryConsensusStateResponse.json (1)
`2-4`: The JSON schema definitions for `queryConsensusStateResponse` are clear and well-documented. Each parameter is appropriately described, which should help in understanding the data structure.source/json_tables/chain/tendermint/commit.json (1)
`2-5`: The JSON schema definitions for `commit` are clear and well-documented. Each parameter is appropriately described, which should help in understanding the commit structure in Tendermint.source/json_tables/chain/tendermint/commitSig.json (1)
`2-5`: The JSON schema definitions for `commitSig` are clear and well-documented. Each parameter is appropriately described, which should help in understanding the commit signature structure in Tendermint.source/json_tables/chain/ibc/core/channel/queryPacketCommitmentsRequest.json (1)
`2-4`: The JSON schema definitions for `queryPacketCommitmentsRequest` are clear and well-documented. Each parameter is appropriately described, which should help in understanding the packet commitments request structure in IBC core channel.source/json_tables/chain/ibc/core/channel/queryUnreceivedAcksRequest.json (1)
`2-4`: The JSON schema definitions for `queryUnreceivedAcksRequest` are clear and well-documented. Each parameter is appropriately described, which should help in understanding the unreceived acknowledgments request structure in IBC core channel.source/json_tables/chain/ibc/core/channel/packetState.json (1)
`2-5`: The JSON schema definitions for `packetState` are clear and well-documented. Each parameter is appropriately described, which should help in understanding the packet state structure in IBC core channel.source/json_tables/chain/ibc/core/channel/queryChannelConsensusStateResponse.json (1)
`1-6`: The JSON schema for `queryChannelConsensusStateResponse` is well-defined and clear.source/json_tables/chain/ibc/core/channel/queryChannelConsensusStateRequest.json (1)
`1-6`: The JSON schema for `queryChannelConsensusStateRequest` is well-defined, with clear descriptions and appropriate required flags.source/json_tables/chain/ibc/core/channel/queryPacketAcknowledgementsRequest.json (1)
`1-6`: The JSON schema for `queryPacketAcknowledgementsRequest` is well-defined. The inclusion of optional pagination and packet sequences is appropriate for flexible query capabilities.source/json_tables/chain/ibc/core/channel/channel.json (1)
`1-7`: The JSON schema for `channel` is comprehensive and well-structured, covering all essential aspects of an IBC channel.source/json_tables/chain/tendermint/abciQueryResponse.json (1)
`1-11`: The JSON schema for `abciQueryResponse` is comprehensive, covering all necessary fields for an ABCI query response in Tendermint.source/json_tables/chain/tendermint/defaultNodeInfo.json (1)
`1-10`: The JSON schema for `defaultNodeInfo` is well-defined, providing a clear and comprehensive description of a Tendermint node's default information.source/index.html.md (1)
`39-45`: The updates to the `index.html.md` file correctly include new documentation sections for `ibccorechannel`, `ibccoreclient`, `ibctransfer`, and `tendermint`. This aligns with the PR's objectives to enhance documentation for these modules.source/json_tables/chain/ibc/core/channel/identifiedChannel.json (1)
`1-8`: The JSON structure and parameter descriptions are clear and consistent.source/json_tables/chain/ibc/transfer/msgTransfer.json (1)
`1-9`: The JSON structure and parameter descriptions are clear and consistent.source/json_tables/chain/tendermint/header.json (1)
`1-15`: The JSON structure and parameter descriptions are clear and consistent.source/includes/_ibccoreclient.md (1)
`116-118`: Ensure the HTML table accurately reflects all necessary parameters as per the JSON schema.source/includes/_account.md (27)
`197-197`: Ensure consistent use of HTML line breaks for visual separation. --- `229-229`: Ensure consistent use of HTML line breaks for visual separation. --- `249-249`: Ensure consistent use of HTML line breaks for visual separation. --- `259-259`: Ensure consistent use of HTML line breaks for visual separation. --- `268-268`: Ensure consistent use of HTML line breaks for visual separation. --- `277-277`: Ensure consistent use of HTML line breaks for visual separation. --- `287-287`: Ensure consistent use of HTML line breaks for visual separation. --- `485-485`: Ensure consistent use of HTML line breaks for visual separation. --- `517-517`: Ensure consistent use of HTML line breaks for visual separation. --- `537-537`: Ensure consistent use of HTML line breaks for visual separation. --- `547-547`: Ensure consistent use of HTML line breaks for visual separation. --- `556-556`: Ensure consistent use of HTML line breaks for visual separation. --- `565-565`: Ensure consistent use of HTML line breaks for visual separation. --- `575-575`: Ensure consistent use of HTML line breaks for visual separation. --- `783-783`: Ensure consistent use of HTML line breaks for visual separation. --- `815-815`: Ensure consistent use of HTML line breaks for visual separation. --- `835-835`: Ensure consistent use of HTML line breaks for visual separation. --- `845-845`: Ensure consistent use of HTML line breaks for visual separation. --- `854-854`: Ensure consistent use of HTML line breaks for visual separation. --- `863-863`: Ensure consistent use of HTML line breaks for visual separation. --- `873-873`: Ensure consistent use of HTML line breaks for visual separation. --- Line range hint `881-881`: Ensure consistent use of HTML line breaks for visual separation. --- `1113-1113`: Ensure consistent use of HTML line breaks for visual separation. --- `1133-1133`: Ensure consistent use of HTML line breaks for visual separation. --- `1152-1152`: Ensure consistent use of HTML line breaks for visual separation. --- `1161-1161`: Ensure consistent use of HTML line breaks for visual separation. --- `1170-1170`: Ensure consistent use of HTML line breaks for visual separation.
NOTE: Do not merge this PR until Python SDK v1.6.0 is released in master
Solves CHAIN-82
Summary by CodeRabbit