InjectiveLabs / docs

Injective Protocol Documentation
Apache License 2.0
16 stars 5 forks source link

Feat/ibc client module queries #166

Closed aarmoa closed 2 months ago

aarmoa commented 6 months ago

NOTE: Do not merge this PR until Python SDK v1.6.0 is released in master

Solves CHAIN-82

Summary by CodeRabbit

coderabbitai[bot] commented 6 months ago

Walkthrough

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.

Changes

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. 🎉


Recent Review Details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
Commits Files that changed from the base of the PR and between 06bb030e0cab07c5d2f70eae2c96b99ebfa60bb3 and b195cc1eac65d7f7cc08fb4a1965c736838ab7d4.
Files selected for processing (102) * source/includes/_account.md (28 hunks) * source/includes/_binaryoptions.md (53 hunks) * source/includes/_chainexchange.md (40 hunks) * source/includes/_changelog.md (1 hunks) * source/includes/_derivatives.md (97 hunks) * source/includes/_ibccoreclient.md (1 hunks) * source/includes/_ibctransfer.md (1 hunks) * source/includes/_spot.md (60 hunks) * source/includes/_staking.md (42 hunks) * source/index.html.md (1 hunks) * source/json_tables/chain/ibc/core/channel/channel.json (1 hunks) * source/json_tables/chain/ibc/core/channel/counterparty.json (1 hunks) * source/json_tables/chain/ibc/core/channel/identifiedChannel.json (1 hunks) * source/json_tables/chain/ibc/core/channel/order.json (1 hunks) * source/json_tables/chain/ibc/core/channel/packetState.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryChannelClientStateRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryChannelClientStateResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryChannelConsensusStateRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryChannelConsensusStateResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryChannelRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryChannelResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryChannelsRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryChannelsResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryConnectionChannelsRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryConnectionChannelsResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryNextSequenceReceiveRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryNextSequenceReceiveResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryPacketAcknowledgementRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryPacketAcknowledgementResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryPacketAcknowledgementsRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryPacketAcknowledgementsResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryPacketCommitmentRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryPacketCommitmentResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryPacketCommitmentsRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryPacketCommitmentsResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryPacketReceiptRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryPacketReceiptResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryUnreceivedAcksRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryUnreceivedAcksResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryUnreceivedPacketsRequest.json (1 hunks) * source/json_tables/chain/ibc/core/channel/queryUnreceivedPacketsResponse.json (1 hunks) * source/json_tables/chain/ibc/core/channel/state.json (1 hunks) * source/json_tables/chain/ibc/core/client/consensusStateWithHeight.json (1 hunks) * source/json_tables/chain/ibc/core/client/identifiedClientState.json (1 hunks) * source/json_tables/chain/ibc/core/client/params.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryClientParamsResponse.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryClientStateRequest.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryClientStateResponse.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryClientStatesRequest.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryClientStatesResponse.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryClientStatusRequest.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryClientStatusResponse.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryConsensusStateHeightsRequest.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryConsensusStateHeightsResponse.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryConsensusStateRequest.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryConsensusStateResponse.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryConsensusStatesRequest.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryConsensusStatesResponse.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryUpgradedClientStateResponse.json (1 hunks) * source/json_tables/chain/ibc/core/client/queryUpgradedConsensusStateResponse.json (1 hunks) * source/json_tables/chain/ibc/core/height.json (1 hunks) * source/json_tables/chain/ibc/transfer/denomTrace.json (1 hunks) * source/json_tables/chain/ibc/transfer/msgTransfer.json (1 hunks) * source/json_tables/chain/ibc/transfer/queryDenomHashRequest.json (1 hunks) * source/json_tables/chain/ibc/transfer/queryDenomHashResponse.json (1 hunks) * source/json_tables/chain/ibc/transfer/queryDenomTraceRequest.json (1 hunks) * source/json_tables/chain/ibc/transfer/queryDenomTraceResponse.json (1 hunks) * source/json_tables/chain/ibc/transfer/queryDenomTracesRequest.json (1 hunks) * source/json_tables/chain/ibc/transfer/queryDenomTracesResponse.json (1 hunks) * source/json_tables/chain/ibc/transfer/queryEscrowAddressRequest.json (1 hunks) * source/json_tables/chain/ibc/transfer/queryEscrowAddressResponse.json (1 hunks) * source/json_tables/chain/ibc/transfer/queryTotalEscrowForDenomRequest.json (1 hunks) * source/json_tables/chain/ibc/transfer/queryTotalEscrowForDenomResponse.json (1 hunks) * source/json_tables/chain/tendermint/abciQueryRequest.json (1 hunks) * source/json_tables/chain/tendermint/abciQueryResponse.json (1 hunks) * source/json_tables/chain/tendermint/block.json (1 hunks) * source/json_tables/chain/tendermint/blockID.json (1 hunks) * source/json_tables/chain/tendermint/blockIDFlag.json (1 hunks) * source/json_tables/chain/tendermint/commit.json (1 hunks) * source/json_tables/chain/tendermint/commitSig.json (1 hunks) * source/json_tables/chain/tendermint/consensus.json (1 hunks) * source/json_tables/chain/tendermint/data.json (1 hunks) * source/json_tables/chain/tendermint/defaultNodeInfo.json (1 hunks) * source/json_tables/chain/tendermint/defaultNodeInfoOther.json (1 hunks) * source/json_tables/chain/tendermint/evidence.json (1 hunks) * source/json_tables/chain/tendermint/evidenceList.json (1 hunks) * source/json_tables/chain/tendermint/getBlockByHeightRequest.json (1 hunks) * source/json_tables/chain/tendermint/getBlockByHeightResponse.json (1 hunks) * source/json_tables/chain/tendermint/getLatestBlockResponse.json (1 hunks) * source/json_tables/chain/tendermint/getLatestValidatorSetResponse.json (1 hunks) * source/json_tables/chain/tendermint/getNodeInfoResponse.json (1 hunks) * source/json_tables/chain/tendermint/getSyncingResponse.json (1 hunks) * source/json_tables/chain/tendermint/getValidatorSetByHeightRequest.json (1 hunks) * source/json_tables/chain/tendermint/getValidatorSetByHeightResponse.json (1 hunks) * source/json_tables/chain/tendermint/header.json (1 hunks) * source/json_tables/chain/tendermint/module.json (1 hunks) * source/json_tables/chain/tendermint/partSetHeader.json (1 hunks) * source/json_tables/chain/tendermint/proofOp.json (1 hunks) * source/json_tables/chain/tendermint/proofOps.json (1 hunks) * source/json_tables/chain/tendermint/protocolVersion.json (1 hunks) * source/json_tables/chain/tendermint/validator.json (1 hunks) * source/json_tables/chain/tendermint/versionInfo.json (1 hunks)
Files not summarized due to errors (2) * source/includes/_ibccoreclient.md: Error: Message exceeds token limit * source/includes/_ibctransfer.md: Error: Message exceeds token limit
Files not reviewed due to errors (7) * source/json_tables/chain/ibc/core/client/queryClientStatusResponse.json (no review received) * source/json_tables/chain/ibc/core/client/queryClientParamsResponse.json (no review received) * source/json_tables/chain/ibc/transfer/queryDenomTraceResponse.json (no review received) * source/json_tables/chain/ibc/transfer/queryEscrowAddressResponse.json (no review received) * source/json_tables/chain/ibc/transfer/queryDenomTraceRequest.json (no review received) * source/json_tables/chain/ibc/core/client/queryClientStatusRequest.json (no review received) * source/json_tables/chain/ibc/core/client/queryUpgradedClientStateResponse.json (no review received)
Files skipped from review due to trivial changes (34) * source/json_tables/chain/ibc/core/channel/counterparty.json * source/json_tables/chain/ibc/core/channel/order.json * source/json_tables/chain/ibc/core/channel/queryChannelClientStateRequest.json * source/json_tables/chain/ibc/core/channel/queryChannelClientStateResponse.json * source/json_tables/chain/ibc/core/channel/queryChannelRequest.json * source/json_tables/chain/ibc/core/channel/queryChannelsResponse.json * source/json_tables/chain/ibc/core/channel/queryConnectionChannelsRequest.json * source/json_tables/chain/ibc/core/channel/queryConnectionChannelsResponse.json * source/json_tables/chain/ibc/core/channel/queryNextSequenceReceiveResponse.json * source/json_tables/chain/ibc/core/channel/queryPacketAcknowledgementResponse.json * source/json_tables/chain/ibc/core/channel/queryPacketAcknowledgementsResponse.json * source/json_tables/chain/ibc/core/channel/queryPacketCommitmentRequest.json * source/json_tables/chain/ibc/core/channel/queryPacketCommitmentResponse.json * source/json_tables/chain/ibc/core/channel/queryUnreceivedPacketsRequest.json * source/json_tables/chain/ibc/core/channel/state.json * source/json_tables/chain/ibc/core/client/queryClientStateRequest.json * source/json_tables/chain/ibc/core/client/queryClientStateResponse.json * source/json_tables/chain/ibc/core/client/queryClientStatesResponse.json * source/json_tables/chain/ibc/core/client/queryConsensusStateHeightsResponse.json * source/json_tables/chain/ibc/core/client/queryConsensusStatesRequest.json * source/json_tables/chain/ibc/core/client/queryConsensusStatesResponse.json * source/json_tables/chain/ibc/transfer/queryDenomHashResponse.json * source/json_tables/chain/ibc/transfer/queryDenomTracesResponse.json * source/json_tables/chain/ibc/transfer/queryTotalEscrowForDenomRequest.json * source/json_tables/chain/ibc/transfer/queryTotalEscrowForDenomResponse.json * source/json_tables/chain/tendermint/block.json * source/json_tables/chain/tendermint/blockIDFlag.json * source/json_tables/chain/tendermint/evidenceList.json * source/json_tables/chain/tendermint/getBlockByHeightRequest.json * source/json_tables/chain/tendermint/getLatestValidatorSetResponse.json * source/json_tables/chain/tendermint/getSyncingResponse.json * source/json_tables/chain/tendermint/getValidatorSetByHeightResponse.json * source/json_tables/chain/tendermint/proofOps.json * source/json_tables/chain/tendermint/versionInfo.json
Additional comments not posted (87)
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.
---
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.