Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(x/staking-upgrade): fix proto broken links #20202

Closed
wants to merge 4 commits into from

Conversation

kien6034
Copy link
Contributor

@kien6034 kien6034 commented Apr 28, 2024

Description

Closes: #XXXX


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

Summary by CodeRabbit

  • Documentation
    • Updated URLs in documentation to reflect the latest versions of protobuf definitions in the Cosmos SDK repository.
  • Refactor
    • Adjusted links from older version branches to the main branch for various modules, ensuring documentation accuracy and up-to-date references.

Copy link
Contributor

coderabbitai bot commented Apr 28, 2024

Walkthrough

The changes in this update focus on aligning the URLs in the x/staking and x/upgrade modules of the Cosmos SDK with the main branch, replacing references to the v0.47.0-rc1 version. This ensures that the documentation accurately reflects the current state of the codebase.

Changes

Files Change Summary
x/staking/README.md, x/staking/proto/.../staking.proto, x/staking/proto/.../tx.proto Updated URLs from v0.47.0-rc1 to main branch for various protobuf definitions. Line numbers and sections adjusted accordingly to match the current state in main.
x/upgrade/README.md, x/upgrade/proto/.../tx.proto URL updates from v0.47.0-rc1 to main branch for protobuf definitions in the x/upgrade module.

Possibly related issues


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

@kien6034
Copy link
Contributor Author

@julienrbrt this PR fixes deprecated broken links in modules (broke when sdk go to 50 i guess).

Can you please review this PR see if this changes is correct. If yes, i will update other modules later)

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Out of diff range and nitpick comments (5)
x/upgrade/README.md (3)

Line range hint 9-18: Consider revising the abstract for grammatical accuracy and clarity.

- `x/upgrade` is an implementation of a Cosmos SDK module that facilitates smoothly
- upgrading a live Cosmos chain to a new (breaking) software version. It accomplishes this by
- providing a `PreBlocker` hook that prevents the blockchain state machine from
- proceeding once a pre-defined upgrade block height has been reached.
+ `x/upgrade` implements a Cosmos SDK module that facilitates the smooth
+ upgrading of a live Cosmos chain to a new (breaking) software version. It achieves this by
+ providing a `PreBlocker` hook that prevents the blockchain state machine from
+ proceeding past a pre-defined upgrade block height.

Line range hint 37-83: Correct typographical errors and ensure terminology consistency in the Concepts section.

- This tool is [Cosmovisor](https://github.com/cosmos/cosmos-sdk/tree/main/tools/cosmovisor#readme).
+ This tool is [Cosmovisor](https://github.com/cosmos/cosmos-sdk/tree/main/tools/cosmovisor).
- `Handler` defines what state migrations need to occur before the new binary Y
+ `Handler` defines the state migrations needed before the new binary Y
- This `StoreLoader` is also application specific and not defined on a per-module basis.
+ This `StoreLoader` is also application-specific and not defined on a per-module basis.

Line range hint 619-619: Correct the Markdown link formatting in the Resources section.

- * [Cosmos Dev Series: Cosmos Blockchain Upgrade](https://medium.com/web3-surfers/cosmos-...
+ * [Cosmos Dev Series: Cosmos Blockchain Upgrade](https://medium.com/web3-surfers/cosmos-dev-series-cosmos-sdk-based-blockchain-upgrade-b5e99181554c)
x/staking/README.md (2)

174-174: Consider rephrasing to "the transaction owner is the bond owner" for conciseness.


627-631: Consider adding a space after the period for better readability.

Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't link main but a tagged version or a commit. Otherwise it gets wrong fast.

Copy link
Contributor Author

@kien6034 kien6034 May 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@julienrbrt sorry for the late update, i took some days off for our holiday. Should we do this instead?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets use a tag, there isnt much benefit to a commit here

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Out of diff range and nitpick comments (9)
x/upgrade/README.md (9)

Line range hint 9-9: Ensure the sentence starts with an uppercase letter for consistency and professionalism.


Line range hint 11-11: Correct the possible spelling mistake: "blockchain stat..." should be "blockchain state..."


Line range hint 16-17: Consider rephrasing to be more concise: "all of the validators need to pause their state machines at exactly the same point" could be "all validators must pause their state machines at the same point."


Line range hint 37-37: Capitalize only proper nouns. Change "Name" to "name" unless it is a specific code element that requires capitalization.


Line range hint 65-65: This expression is usually spelled with a hyphen: "application-specific."


Line range hint 136-136: Correct the possible spelling mistake: "big endian" should be "big-endian" when used as an adjective.


Line range hint 149-149: Consider a shorter alternative to "Any and all proposal related events are emitted through the x/gov module" such as "All proposal-related events are emitted through the x/gov module."


Line range hint 166-166: Ensure the sentence starts with an uppercase letter for consistency and professionalism.


Line range hint 619-619: Ensure all markdown links are correctly formatted. It seems there might be an unpaired '[' symbol.

@tac0turtle
Copy link
Member

closing, reopen if needed.

@tac0turtle tac0turtle closed this May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants