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

chore: readmes + upgrading docs #21271

Merged
merged 17 commits into from
Aug 15, 2024
Merged

chore: readmes + upgrading docs #21271

merged 17 commits into from
Aug 15, 2024

Conversation

julienrbrt
Copy link
Member

@julienrbrt julienrbrt commented Aug 13, 2024

Description

Prepares readme + upgrading.md for alpha


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, you can find examples of the prefixes below:
  • 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.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

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

  • New Features

    • Enhanced ability to overwrite configuration settings.
    • Introduced a new query command for backward compatibility.
    • Added a new helper method for broadcasting test transactions.
    • Improved features in the collections module.
  • Bug Fixes

    • Improved error handling during initialization and transaction processing.
    • Refined handling of gas fees to prevent potential issues.
  • Documentation

    • Updated documentation for clearer module dependencies and compatibility information.
    • Added migration instructions for transitioning to the latest version.
    • Enhanced clarity in tool documentation regarding usage and compatibility.

Copy link
Contributor

coderabbitai bot commented Aug 13, 2024

Walkthrough

Walkthrough

This update introduces significant enhancements across the Cosmos SDK, focusing on improved user experience, modularity, and the removal of deprecated functionalities. Key features include the ability to overwrite client.toml configurations, the addition of the wait-tx command for backward compatibility, refined error handling, and crucial updates to documentation for better clarity on dependencies and migration processes. The release emphasizes maintaining backward compatibility while phasing out legacy components, ensuring a smoother transition for developers.

Changes

Files Change Summary
CHANGELOG.md Introduces enhancements, bug fixes, and breaking changes across modules. Features include wait-tx command and improved MsgRouter. Emphasizes removal of deprecated functionalities.
README.md Updates documentation on core and module dependencies for clarity and conciseness, consolidating information on compatibility across SDK versions.
UPGRADING.md Adds migration documentation for version v0.52.x, clarifies module handling, and updates buf.gen.gogo.yaml configuration for new package location of codectypes.Any.
collections/CHANGELOG.md Organizes feature entries for better clarity, highlights new Quad feature, and improves readability through adjusted formatting.
tools/confix/CHANGELOG.md Changes header from "### Features" to a specific version release, enhancing clarity on features related to versioning.
tools/confix/README.md Introduces sections on usage tips and compatibility, providing a table for SDK and confix version relationships to improve usability.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant CosmosSDK
    participant Documentation
    Developer->>CosmosSDK: Use new features (e.g., wait-tx)
    CosmosSDK-->>Developer: Processes transaction
    Developer->>Documentation: Check compatibility
    Documentation-->>Developer: Provides dependency information
Loading
sequenceDiagram
    participant Developer
    participant MigrationDocs
    Developer->>MigrationDocs: Access migration info for v0.52.x
    MigrationDocs-->>Developer: Provides necessary updates
Loading

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.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

@github-actions github-actions bot added the C:Confix Issues and PR related to Confix label Aug 13, 2024
@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Aug 13, 2024
@julienrbrt julienrbrt marked this pull request as ready for review August 14, 2024 12:03
@julienrbrt julienrbrt requested a review from a team as a code owner August 14, 2024 12:03
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

Outside diff range, codebase verification and nitpick comments (14)
collections/CHANGELOG.md (1)

37-37: Add a comma before "but".

The sentence "It is basic wrapping of the standard Map methods but is not iterable." would be clearer with a comma before "but".

- Add LookupMap implementation. It is basic wrapping of the standard Map methods but is not iterable.
+ Add LookupMap implementation. It is basic wrapping of the standard Map methods, but is not iterable.
Tools
LanguageTool

[uncategorized] ~37-~37: Possible missing comma found.
Context: ...sic wrapping of the standard Map methods but is not iterable. * [#19343](https://git...

(AI_HYDRA_LEO_MISSING_COMMA)

tools/confix/README.md (1)

42-44: Clarify the implications of using confix directly in the application.

The tip mentions that using confix directly in the application can have fewer features than using it standalone. It would be helpful to specify which features might be missing or affected.

README.md (1)

69-70: Reword to avoid repetition.

The sentence "Core dependencies are the core libraries that an application may depend on. Core dependencies not mentionned here as compatible across all maintained SDK versions." repeats the phrase "Core dependencies". Consider rewording for clarity.

- Core dependencies are the core libraries that an application may depend on. Core dependencies not mentionned here as compatible across all maintained SDK versions.
+ Core dependencies are the libraries that an application may depend on. Those not mentioned here are compatible across all maintained SDK versions.
Tools
LanguageTool

[style] ~69-~69: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ries that an application may depend on. Core dependencies not mentionned here as com...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

UPGRADING.md (5)

Line range hint 10-10: Clarify the use of "Note".

The phrase "Note, always read the SimApp section for more information on application wiring updates." could be clearer. Consider rephrasing for better readability.

- Note, always read the **SimApp** section for more information on application wiring updates.
+ Note: Always read the **SimApp** section for more information on application wiring updates.
Tools
LanguageTool

[typographical] ~49-~49: It appears that a comma is missing.
Context: ...es described here. ### SimApp In this section we describe the changes made in Cosmos ...

(DURING_THAT_TIME_COMMA)


42-42: Improve link clarity.

The link to the release tag could be more descriptive to enhance readability.

- [v0.52.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.52.0-alpha.0)
+ [v0.52.x Release Notes](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.52.0-alpha.0)

44-45: Clarify migration documentation availability.

The sentence "Documentation to migrate an application from v0.50.x to server/v2 is available elsewhere." could specify where the documentation is available for better guidance.

- Documentation to migrate an application from v0.50.x to server/v2 is available elsewhere.
+ Documentation for migrating an application from v0.50.x to server/v2 is available in the [migration guide](link-to-migration-guide).

211-211: Clarify the type relocation.

The sentence "The codectypes.Any has moved to github.com/cosmos/gogoproto/types/any." could be more precise by specifying that it's a package relocation.

- The `codectypes.Any` has moved to `github.com/cosmos/gogoproto/types/any`.
+ The `codectypes.Any` type has been relocated to the package `github.com/cosmos/gogoproto/types/any`.

218-219: Ensure YAML configuration clarity.

The YAML configuration snippet could include a brief explanation of the changes to help users understand the context.

```diff
version: v1
plugins:
  - name: gocosmos
    out: ..
-    opt: plugins=grpc,Mgoogle/protobuf/any.proto=github.com/cosmos/cosmos-sdk/codec/types,Mcosmos/orm/v1/orm.proto=cosmossdk.io/orm
+    opt: plugins=grpc,Mgoogle/protobuf/any.proto=github.com/cosmos/gogoproto/types/any,Mcosmos/orm/v1/orm.proto=cosmossdk.io/orm
  - name: grpc-gateway
    out: ..
    opt: logtostderr=true,allow_colon_final_segments=true

</blockquote></details>
<details>
<summary>CHANGELOG.md (6)</summary><blockquote>

`46-46`: **Add a period at the end of the sentence.**

The sentence "Simulate nested messages" should end with a period for consistency with other entries.

```diff
- Simulate nested messages
+ Simulate nested messages.

57-57: Clarify the usage of client.CreateClientConfig.

The sentence "Use client.CreateClientConfig in place of client.ReadFromClientConfig" could be more explicit about the context or reason for this change.

Consider adding a brief explanation of why this change was made.


60-60: Correct the term "test e2e tests".

The phrase "test e2e tests" is redundant. Consider rephrasing for clarity.

- to broadcast test txns to test e2e tests.
+ to broadcast transactions for end-to-end (e2e) tests.

125-125: Clarify the description of the bug fix.

The description "won't terminate when a key is not found" could be more explicit about the behavior change.

Consider rephrasing to "The keys delete command now handles missing keys gracefully without terminating."


137-137: Ensure consistent use of punctuation.

The sentence "do not take a home directory anymore" should end with a period for consistency.

- do not take a home directory anymore
+ do not take a home directory anymore.

219-219: Add a period at the end of the sentence.

The sentence "use keeper.AccountsModKeeper.NextAccountNumber instead" should end with a period for consistency with other entries.

- use `keeper.AccountsModKeeper.NextAccountNumber` instead
+ use `keeper.AccountsModKeeper.NextAccountNumber` instead.
Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7f1dd97 and 1079805.

Files selected for processing (6)
  • CHANGELOG.md (3 hunks)
  • README.md (1 hunks)
  • UPGRADING.md (3 hunks)
  • collections/CHANGELOG.md (2 hunks)
  • tools/confix/CHANGELOG.md (1 hunks)
  • tools/confix/README.md (2 hunks)
Files skipped from review due to trivial changes (1)
  • tools/confix/CHANGELOG.md
Additional context used
Path-based instructions (5)
collections/CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

tools/confix/README.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

README.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

UPGRADING.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

LanguageTool
collections/CHANGELOG.md

[uncategorized] ~37-~37: Possible missing comma found.
Context: ...sic wrapping of the standard Map methods but is not iterable. * [#19343](https://git...

(AI_HYDRA_LEO_MISSING_COMMA)

README.md

[style] ~69-~69: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ries that an application may depend on. Core dependencies not mentionned here as com...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

Additional comments not posted (1)
tools/confix/README.md (1)

144-152: Compatibility section looks good.

The addition of the compatibility section is clear and informative, providing valuable guidance on version compatibility.

@julienrbrt julienrbrt enabled auto-merge August 14, 2024 12:10
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

Outside diff range, codebase verification and nitpick comments (2)
CHANGELOG.md (2)

46-46: Add a period at the end of the sentence.

The sentence "Simulate nested messages" should end with a period for consistency.

- Simulate nested messages
+ Simulate nested messages.

68-68: Clarify the purpose of IsGT method.

The description of the IsGT method for types.Coin could be expanded to explain its typical use cases or scenarios where it would be beneficial.

Consider adding a brief explanation of when and why this method should be used.

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1079805 and d7f2975.

Files selected for processing (1)
  • CHANGELOG.md (2 hunks)
Additional context used
Path-based instructions (1)
CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

Additional comments not posted (5)
CHANGELOG.md (5)

60-60: Clarify the usage of client.CreateClientConfig.

The change mentions using client.CreateClientConfig in place of client.ReadFromClientConfig, but does not explain the implications of this change.

Clarify whether this change affects existing configurations and if any migration steps are necessary.


74-74: Clarify the role of core/transaction.Service.

The addition of core/transaction.Service in runtime is mentioned, but its purpose and impact on existing functionality are not clear.

Provide more context on how this service integrates with the existing architecture and its benefits.


134-134: Clarify the impact of renaming SetProtocolVersion.

The change from SetProtocolVersion to SetAppVersion should include any necessary steps developers need to take to accommodate this change.

Ensure that the documentation provides guidance on updating code that relies on the old method name.


140-140: Clarify changes to key output functions.

The change to clientkeys.NewKeyOutput and related functions now taking an address codec should include examples or guidance on how to update existing code.

Include examples of how to use the new function signatures.


194-194: Clarify changes to HasAminoCodec.

The change to the HasAminoCodec signature should include examples or guidance on how to update existing code.

Provide examples of how to use the updated interface.

@julienrbrt julienrbrt disabled auto-merge August 15, 2024 13:47
Copy link
Contributor

@hieuvubk hieuvubk left a comment

Choose a reason for hiding this comment

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

LGTM

CHANGELOG.md Show resolved Hide resolved
CHANGELOG.md Show resolved Hide resolved
CHANGELOG.md Show resolved Hide resolved
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

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d7f2975 and a50542b.

Files selected for processing (1)
  • CHANGELOG.md (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • CHANGELOG.md

@julienrbrt julienrbrt added this pull request to the merge queue Aug 15, 2024
@julienrbrt julienrbrt removed this pull request from the merge queue due to a manual request Aug 15, 2024
@julienrbrt julienrbrt added this pull request to the merge queue Aug 15, 2024
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

Outside diff range, codebase verification and nitpick comments (3)
CHANGELOG.md (3)

57-60: Clarify Feature Description.

The feature description for overwriting client.toml could be clearer. Consider breaking it into multiple lines for readability.

- * (client) [#17513](https://github.com/cosmos/cosmos-sdk/pull/17513) Allow overwriting `client.toml`. Use `client.CreateClientConfig` in place of `client.ReadFromClientConfig` and provide a custom template and a custom config.
+ * (client) [#17513](https://github.com/cosmos/cosmos-sdk/pull/17513) Allow overwriting `client.toml`.
+   Use `client.CreateClientConfig` instead of `client.ReadFromClientConfig` and provide a custom template and a custom config.

78-78: Clarify Timeout Timestamp Feature.

The description of the timeout-timestamp feature could benefit from improved clarity and separation of ideas.

- * (client/tx) [#20870](https://github.com/cosmos/cosmos-sdk/pull/20870) Add `timeout-timestamp` field for tx body defines time based timeout.Add `WithTimeoutTimestamp` to tx factory. Increased gas cost for processing newly added timeout timestamp field in tx body.
+ * (client/tx) [#20870](https://github.com/cosmos/cosmos-sdk/pull/20870) Add `timeout-timestamp` field to define a time-based timeout in the transaction body.
+   Add `WithTimeoutTimestamp` to the transaction factory. Increased gas cost for processing the newly added timeout timestamp field in the transaction body.

126-126: Clarify Bug Fix Description.

The description for the keys delete bug fix could be more explicit about the behavior change.

- * (client/keys) [#18562](https://github.com/cosmos/cosmos-sdk/pull/18562) `keys delete` won't terminate when a key is not found.
+ * (client/keys) [#18562](https://github.com/cosmos/cosmos-sdk/pull/18562) Updated `keys delete` command to handle cases where a key is not found without terminating.
Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a50542b and 5deb0c3.

Files selected for processing (2)
  • CHANGELOG.md (2 hunks)
  • tools/confix/CHANGELOG.md (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • tools/confix/CHANGELOG.md
Additional context used
Path-based instructions (1)
CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

Additional comments not posted (2)
CHANGELOG.md (2)

46-46: Ensure Consistent Formatting.

The "Features" section should be consistently formatted with sub-bullets where applicable. Reviewers have noted potential missing sub-bullets.

Verification successful

Ensure Consistent Use of Sub-Bullets in "Features" Section

The "Features" section in the CHANGELOG.md file does not consistently use sub-bullets, which can lead to confusion about the structure and hierarchy of the information presented. Please review and adjust the formatting to ensure clarity and consistency.

  • Consider using sub-bullets for related items or additional details under each feature to maintain a uniform structure across the changelog.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify consistent use of sub-bullets in the "Features" section.
# Test: Check for sub-bullets in the "Features" section.
rg --type md -A 5 $'### Features\n*' CHANGELOG.md

Length of output: 241


Script:

#!/bin/bash
# Description: Verify consistent use of sub-bullets in the "Features" section.
# Test: Check for sub-bullets in the "Features" section using multiline mode.
rg --type md --multiline -A 5 $'### Features\n*' CHANGELOG.md

Length of output: 18924


134-134: Ensure Consistent Formatting.

The "API Breaking Changes" section should be consistently formatted with sub-bullets where applicable. Reviewers have noted potential missing sub-bullets.

Merged via the queue into main with commit 858ec2f Aug 15, 2024
69 of 72 checks passed
@julienrbrt julienrbrt deleted the julien/cls branch August 15, 2024 19:47
mergify bot pushed a commit that referenced this pull request Aug 15, 2024
(cherry picked from commit 858ec2f)

# Conflicts:
#	CHANGELOG.md
#	UPGRADING.md
#	collections/CHANGELOG.md
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

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a50542b and 5deb0c3.

Files selected for processing (2)
  • CHANGELOG.md (2 hunks)
  • tools/confix/CHANGELOG.md (1 hunks)
Files skipped from review as they are similar to previous changes (2)
  • CHANGELOG.md
  • tools/confix/CHANGELOG.md

julienrbrt added a commit that referenced this pull request Aug 15, 2024
alpe added a commit that referenced this pull request Aug 19, 2024
* main: (76 commits)
  docs: more app v2 renaming (#21336)
  chore: update link in disclaimer (#21339)
  refactor(x/distribution): audit QA (#21316)
  docs: rename app v2 to app di when talking about runtime v0 (#21329)
  feat(schema): specify JSON mapping (#21243)
  fix(x/authz): bring back msg response in `DispatchActions` (#21044)
  chore: fix all lint issue since golangci-lint bump (#21326)
  refactor(x/mint): v0.52 audit x/mint (#21301)
  chore: fix spelling errors (#21327)
  feat: export genesis in simapp v2 (#21199)
  fix(baseapp)!: Halt at height now does not produce the halt height block (#21256)
  refactor(scripts): remove unused variable (#21320)
  chore(schema/testing): upgrade to go 1.23 iterators (#21282)
  chore: readmes + upgrading docs (#21271)
  feat(client): add auto cli for node service (#21074)
  ci: fix github workflow vulnerable to script injection (#21304)
  build(deps): Bump github.com/prometheus/client_golang from 1.19.1 to 1.20.0 (#21307)
  build(deps): use Go 1.23 instead of Go 1.22 (#21280)
  refactor(x/auth): audit x/auth changes (#21146)
  chore: remove todo: "abstract out staking message back to staking" (#21266)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release C:collections C:Confix Issues and PR related to Confix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants