feat(depinject): support for capability

[crodriguezvega]

Description

Adding support for capability package.

ref: #3560

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against the correct branch (see CONTRIBUTING.md).
• Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
• Code follows the module structure standards and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/).
• Added relevant godoc comments.
• Provide a conventional commit message to follow the repository standards.
• Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
• Re-reviewed Files changed in the GitHub PR explorer.
• Review SonarCloud Report in the comment section below once CI passes.

[coderabbitai]

Important

Auto Review Skipped

Auto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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

[crodriguezvega]

I had to delete manually a pg.go file that gets generated. Would there be a way to skip its generation?

[damiannolan]

Looks pretty much good to go so far. I left a couple of nits and a comment about the MemoryStoreKey

Happy to also push some updates from comments myself today if I get to it!

[damiannolan]

This is what enables the custom cosmos module options, right?

i.e.

option (cosmos.app.v1alpha1.module) = {
    go_import: "github.com/cosmos/ibc-go/modules/capability"
};

[crodriguezvega]

yeah, that's my understanding.

[damiannolan]

Can we try doing ADD api api on L13 instead?

[damiannolan]

Attemped to move this to ADD, looks like docker image built successfully. But we are seeing this sonar test failure on all PR workflows at the moment, I think it is outside of our control, assuming somebody somewhere will fix

[damiannolan]

I had to delete manually a pg.go file that gets generated. Would there be a way to skip its generation?

I don't understand why we need to delete that file? Was it just in a single commit where something was funky? The diffs against the target branch don't show a deleted file there so I'm assuming its still in place

[crodriguezvega]

I had to delete manually a pg.go file that gets generated. Would there be a way to skip its generation?

I don't understand why we need to delete that file? Was it just in a single commit where something was funky? The diffs against the target branch don't show a deleted file there so I'm assuming its still in place

When I run make photo-all that pb.go file was created and if I tried to build then it was giving me errors, but since we don't need I just deleted it manually.

[damiannolan]

Eeek, I was a little too quick on slapping the approval. Looks like build failures due to go version discrepancy. Might be worth just bumping all to go1.22 for this work. What do you think?

[crodriguezvega]

Eeek, I was a little too quick on slapping the approval. Looks like build failures due to go version discrepancy. Might be worth just bumping all to go1.22 for this work. What do you think?

Yes, I think it will be the shortest path...

[DimitrisJim]

huh, so workflow file doesn't need to be bumped? That's odd, I thought this directive enforced something about the version of go you're running, apparently not?

[damiannolan]

I guess we can downgrade this to go1.21 again

[DimitrisJim]

lgtm! love to see everything building fine.

[sonarcloud]

Quality Gate passed for 'ibc-go'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud