chore: make struct comments match struct names

[bytesingsong]

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

• Have you read the CONTRIBUTING.md?
• Does your PR follow the C4 patch requirements?
• Have you rebased your work on top of the latest master?
• Have you checked your code compiles? (make)
• Have you included tests for any non-trivial functionality?
• Have you checked your code passes the unit tests? (make test)
• Have you checked your code formatting is correct? (go fmt)
• Have you checked your basic code style is fine? (golangci-lint run)
• If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
• If your changes affect the client infrastructure, have you run the integration test?
• If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
• If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
• If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

• Documentation
  • Corrected titles and comments in the API and proto documentation to accurately reflect the response type for the ContractByDenom call. No functional changes were made.

[coderabbitai]

Walkthrough

The changes update documentation comments and metadata to accurately reflect that ContractByDenomResponse is the response type for the ContractByDenom call, correcting previous instances where it was mislabeled as ContractByDenomRequest. No structural or functional changes to code or APIs were made.

Changes

File(s)	Change Summary
client/docs/swagger-ui/swagger.yaml	Updated title metadata in two places to reference ContractByDenomResponse instead of ContractByDenomRequest.
proto/cronos/query.proto	Corrected comment to state ContractByDenomResponse is the response type, not ContractByDenomRequest.

Suggested reviewers

• mmsqe
• thomas-nguy

Poem

A typo fixed, a label set right,
The docs now gleam with proper insight.
From request to response, the truth is restored,
Swagger and proto in perfect accord.
🐇✨

Hop along, dear coder, your docs now delight!

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1337bc5 and e2a6a67.

⛔ Files ignored due to path filters (1)

• x/cronos/types/query.pb.go is excluded by !**/*.pb.go

📒 Files selected for processing (2)

• client/docs/swagger-ui/swagger.yaml (2 hunks)
• proto/cronos/query.proto (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• proto/cronos/query.proto
• client/docs/swagger-ui/swagger.yaml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d41d670 and 377bd75.

Files ignored due to path filters (1)

• x/cronos/types/tx.pb.go is excluded by !**/*.pb.go

Files selected for processing (1)

• proto/cronos/tx.proto (1 hunks)

Files skipped from review due to trivial changes (1)

• proto/cronos/tx.proto

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 35.85%. Comparing base (d41d670) to head (377bd75).

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1465       +/-   ##
===========================================
+ Coverage   17.54%   35.85%   +18.31%     
===========================================
  Files          87      136       +49     
  Lines        5273     9806     +4533     
===========================================
+ Hits          925     3516     +2591     
- Misses       4238     5894     +1656     
- Partials      110      396      +286     

see 72 files with indirect coverage changes

[mmsqe]

@bytesingsong can you sign the commit?

[bytesingsong]

@bytesingsong can you sign the commit?

Sorry for deal so late.

Signed. Please review again.