feat(x/distribution): add rewards-by-validator autocli config

[julienrbrt]

Description

DelegationTotalRewards had no autocli config, giving it a weird ux: delegation-total-rewards --delegator-address [addr].
This makes the UX more consistent with v0.47.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

[coderabbitai]

Walkthrough

The update introduces a new RPC method DelegationTotalRewards to the AutoCLIOptions in the AppModule struct, aimed at querying comprehensive distribution rewards for delegators. Additionally, the DelegationRewards RPC method now specifically targets rewards from a singular validator, with its usage updated to rewards-by-validator. This refines the querying capabilities for distribution delegator rewards, offering both a broad and specific perspective on rewards.

Changes

File(s)	Change Summary
x/distribution/autocli.go	Added DelegationTotalRewards RPC method; Updated DelegationRewards usage to rewards-by-validator.

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-tests 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 tests 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 tests.
  • @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[github-actions]

@julienrbrt your pull request is missing a changelog!

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: .coderabbit.yml

Commits

Files that changed from the base of the PR and between 2bf7e9f and 6529d0a.

Files selected for processing (1)

• x/distribution/autocli.go (1 hunks)

Additional comments: 1

x/distribution/autocli.go (1)

• 64-65: The usage of the DelegationRewards RPC method has been updated to "rewards-by-validator [delegator-addr] [validator-addr]", and the short description has been modified accordingly. This change aligns with the PR's objective to enhance the user experience by making the querying process more intuitive.

• Ensure that the documentation and any related user guides are updated to reflect this change in usage.
• Verify that existing scripts or automation tools that rely on the old DelegationRewards usage are identified and updated accordingly to prevent breaking changes.

[julienrbrt]

@julienrbrt your pull request is missing a changelog!

will add in v0.50 backport (x/distribution isn't split there so it should be in the main changelog, but here needs to be added in x/distribution/changelog)