v0.20.1 add stargate queries to wasmOpts

[hard-nett]

Summary by CodeRabbit

• New Features

  • Enhanced query capabilities for IBC connections and other modules.
  • Integration of Stargate queries for improved inter-module communication.

• Bug Fixes

  • Updated handling of accepted queries to ensure accurate responses.

• Documentation

  • Clarified the structure and functionality of the AppKeepers related to query handling.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in the keepers.go file focus on enhancing the application's query capabilities by integrating Stargate queries. A new import for IBC connection types is added, and the NewAppKeepers function is updated to include a comprehensive mapping of query paths and response types for various modules. The modifications introduce accepted and querierOpts variables to configure query plugins for the Wasm keeper, specifically expanding its ability to handle inter-module queries with improved flexibility.

Changes

File	Change Summary
app/keepers/keepers.go	- Added import for ibcconnectiontypes - Introduced accepted variable for Stargate query paths - Created querierOpts for Wasm keeper query configuration

Sequence Diagram

sequenceDiagram
    participant App as Application
    participant Wasm as WasmKeeper
    participant IBC as IBC Module
    participant Dist as Distribution Module
    participant Staking as Staking Module

    App->>Wasm: Configure Query Plugins
    Wasm-->>App: Query Plugin Configuration
    App->>Wasm: Initialize with Stargate Queries
    Wasm->>IBC: Query IBC Connections
    Wasm->>Dist: Query Distribution
    Wasm->>Staking: Query Staking Information

Loading

Poem

🐰 Queries dance, modules entwine,
Stargate's magic, line by line,
Wasm keeper, now so bright,
Connections leap with pure delight!
A rabbit's code, both swift and keen,
Weaves modules in a cosmic scene 🌟

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

app/keepers/keepers.go (1)

319-341: Stargate query mapping looks comprehensive.

Defining the accepted paths and corresponding response types for IBC, distribution, staking, and FanToken modules ensures a modular and explicit approach. This approach enhances the Wasm keeper's query capabilities.

You could consider including a brief comment/inline doc for each path describing its usage, which would help future maintainers.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e90d994 and aa76c05.

📒 Files selected for processing (1)

• app/keepers/keepers.go (2 hunks)

🔇 Additional comments (3)

app/keepers/keepers.go (3)

65-65: New import for IBC connection types.

This import is essential for handling IBC connection queries and aligns with the new stargate query logic introduced below. Great addition!

---

343-347: Query plugins enhance Wasm's GRPC-based queries.

Using QueryPlugins (particularly the AcceptListStargateQuerier) properly sets up a filtered approach to allowed queries. This is a secure pattern for limiting what queries a Wasm contract can call.

---

348-348: Appending querierOpts to wasmOpts is well-structured.

By appending the newly created QueryPlugins to wasmOpts, you maintain a clean approach to configuring your Wasm keeper. This nicely encapsulates the stargate query logic in a single place.