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: learn/advance #22367

Merged
merged 4 commits into from
Oct 25, 2024
Merged

docs: learn/advance #22367

merged 4 commits into from
Oct 25, 2024

Conversation

JulianToledano
Copy link
Contributor

@JulianToledano JulianToledano commented Oct 25, 2024

Description

Ref:
#21429

Updatea:

  • encoding
  • grpc
  • cli
  • events
  • run-tx

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

  • Documentation
    • Enhanced clarity and structure in the BaseApp, Encoding, gRPC REST, CLI, Events, Telemetry, and RunTx Middleware documents.
    • Updated links and references to reflect the latest version of the Cosmos SDK.
    • Improved explanations around encoding practices, event management, and CLI usage.
    • Added guidelines for Protobuf message definitions and clarified telemetry metrics management.

@JulianToledano JulianToledano requested a review from a team as a code owner October 25, 2024 11:22
Copy link
Contributor

coderabbitai bot commented Oct 25, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request includes extensive documentation updates across multiple files related to the Cosmos SDK. Key changes involve clarifying the functionality of BaseApp, transitioning encoding practices to gogoprotobuf, and updating links to reflect the latest SDK version. Each document has been refined for accuracy, with improved explanations of concepts such as event management, telemetry, and CLI usage. The updates ensure that the documentation aligns with the current state of the Cosmos SDK, enhancing clarity and usability for developers.

Changes

File Path Change Summary
docs/learn/advanced/00-baseapp.md Expanded introduction and type definition sections, refined explanations of volatile states, updated constructor details, elaborated on state updates, and clarified ABCI message roles. Minor formatting changes.
docs/learn/advanced/05-encoding.md Emphasized transition from go-amino to gogoprotobuf, refined wire encoding protocols, updated storage encoding guidelines, clarified codec package descriptions, and added Protobuf message definition guidelines.
docs/learn/advanced/06-grpc_rest.md Updated links to reflect SDK version changes, refined text for clarity, and updated Swagger generation script references.
docs/learn/advanced/07-cli.md Updated CLI references and links, clarified command structure, refined transaction and query command descriptions, and elaborated on flags and environment variables handling.
docs/learn/advanced/08-events.md Updated Protobuf file references, refined Event structure description, improved examples formatting, and clarified EventManager usage.
docs/learn/advanced/09-telemetry.md Updated telemetry API link to the latest version while maintaining overall content structure.
docs/learn/advanced/11-runtx_middleware.md Updated version references for panic recovery implementation and made minor textual corrections.

Possibly related PRs

  • refactor(baseapp): create checktx handler #21979: The changes in the main PR regarding the BaseApp functionality and its lifecycle methods are directly related to the modifications made in this PR, which introduces a CheckTx handler and refines transaction processing logic.
  • docs(core): create docs for environment and core API #22156: This PR enhances the documentation for the core API, which includes the BaseApp and its methods, aligning with the updates made in the main PR that clarify the BaseApp functionalities.
  • docs: update learn/beginner docs #22191: The updates in this PR to the beginner documentation, particularly regarding the BeginBlocker, EndBlocker, and PreBlocker lifecycle methods, are relevant as they complement the changes made in the main PR that also elaborates on these methods.
  • docs: update some learn/advanced #22255: This PR updates the advanced documentation for BaseApp, which is directly related to the changes in the main PR that focus on enhancing the clarity and detail of the BaseApp component.
  • chore(doc): Update sims doc #22258: The updates in this PR regarding the simulation documentation may relate to the transaction lifecycle and processing, which are also discussed in the main PR, although the connection is less direct.

Suggested reviewers

  • julienrbrt
  • tac0turtle
  • akhilkumarpilli

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>, please review it.
    • 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 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 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 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 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.

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.

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: 4

🧹 Outside diff range and nitpick comments (7)
docs/learn/advanced/06-grpc_rest.md (1)

81-81: Consider improving the sentence structure

While the link update is correct, consider rephrasing for better clarity:

-The Cosmos SDK's [Swagger generation script](https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/scripts/protoc-swagger-gen.sh) is a good place to start.
+For generating Swagger definitions, you can refer to the [Swagger generation script](https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/scripts/protoc-swagger-gen.sh) in the Cosmos SDK repository.
docs/learn/advanced/05-encoding.md (3)

37-37: Consider using a version-independent link for collections documentation.

The link to the collections package includes a specific version (v0.4.0). Consider using a version-independent link (e.g., /main/ branch) to ensure the documentation remains current, or add a note indicating which SDK version this documentation corresponds to.


78-78: Consider using version-independent links for code references.

The code references use specific SDK version tags (v0.52.0-beta.1). Consider:

  1. Using version-independent links (e.g., /main/ branch), or
  2. Adding a note specifying which SDK version this documentation targets.

This will help maintain documentation relevance across SDK versions.


146-146: Use more common American English phrasing.

For consistency with American English style:

-Have a look at [a real-life example in the x/auth module]
+Take a look at [a real-life example in the x/auth module]
🧰 Tools
🪛 LanguageTool

[locale-violation] ~146-~146: In American English, “take a look” is more commonly used.
Context: ...face` method to bundle these two steps. Have a look at [a real-life example in the x/auth m...

(HAVE_A_LOOK)

docs/learn/advanced/07-cli.md (2)

40-40: Grammar and style improvements needed

Several grammatical improvements would enhance readability:

  • Line 40: Add a comma before 'so': "persist []bytes, so the developer"
  • Line 60: Add a comma after "credentials": "storage of key credentials, look at"
  • Line 90: Add a comma after "By default": "By default, the app uses"
  • Line 123: Replace "in order to" with "to" for conciseness

Also applies to: 60-60, 90-90, 123-123

🧰 Tools
🪛 LanguageTool

[uncategorized] ~40-~40: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...tion - stores can only persist []bytes so the developer must define a serializati...

(COMMA_COMPOUND_SENTENCE_2)


Line range hint 171-189: Consider enhancing environment variables documentation

The environment variables section could be improved by:

  1. Adding more real-world examples of commonly used environment variables
  2. Including a note about environment variable precedence over flags
  3. Mentioning best practices for managing environment variables in different environments
🧰 Tools
🪛 LanguageTool

[uncategorized] ~169-~169: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...d to commands; some toggle an option off but others are empty values that the user n...

(COMMA_COMPOUND_SENTENCE_2)

docs/learn/advanced/00-baseapp.md (1)

Line range hint 1013-1027: Maintain consistent version references

The code references for ExtendVote and VerifyVoteExtension use different SDK versions (v0.52.0-beta.2 and v0.50.0-alpha.0). For consistency, they should reference the same version.

Update the VerifyVoteExtension reference to use v0.52.0-beta.2:

-https://github.com/cosmos/cosmos-sdk/blob/v0.50.0-alpha.0/baseapp/abci_utils.go#L282-L288
+https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/baseapp/abci_utils.go#L282-L288
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between aa4614e and 3d640e7.

📒 Files selected for processing (7)
  • docs/learn/advanced/00-baseapp.md (2 hunks)
  • docs/learn/advanced/05-encoding.md (6 hunks)
  • docs/learn/advanced/06-grpc_rest.md (3 hunks)
  • docs/learn/advanced/07-cli.md (8 hunks)
  • docs/learn/advanced/08-events.md (3 hunks)
  • docs/learn/advanced/09-telemetry.md (1 hunks)
  • docs/learn/advanced/11-runtx_middleware.md (3 hunks)
🧰 Additional context used
📓 Path-based instructions (7)
docs/learn/advanced/00-baseapp.md (1)

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

docs/learn/advanced/05-encoding.md (1)

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

docs/learn/advanced/06-grpc_rest.md (1)

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

docs/learn/advanced/07-cli.md (1)

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

docs/learn/advanced/08-events.md (1)

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

docs/learn/advanced/09-telemetry.md (1)

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

docs/learn/advanced/11-runtx_middleware.md (1)

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

🪛 LanguageTool
docs/learn/advanced/05-encoding.md

[locale-violation] ~146-~146: In American English, “take a look” is more commonly used.
Context: ...face` method to bundle these two steps. Have a look at [a real-life example in the x/auth m...

(HAVE_A_LOOK)

docs/learn/advanced/07-cli.md

[uncategorized] ~40-~40: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...tion - stores can only persist []bytes so the developer must define a serializati...

(COMMA_COMPOUND_SENTENCE_2)


[style] ~60-~60: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ree/v0.52.0-beta.2/client/keys/add.go). For more details about usage of `--keyring-...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[uncategorized] ~60-~60: Possible missing comma found.
Context: ... --keyring-backend for storage of key credentials look at the [keyring docs](https://docs...

(AI_HYDRA_LEO_MISSING_COMMA)


[style] ~66-~66: Consider removing “of” to be more concise
Context: ...be run before every execution, and adds all of the necessary subcommands. ```go reference...

(ALL_OF_THE)


[uncategorized] ~90-~90: Did you mean: “By default,”?
Context: .../simapp/simd/cmd/config.go#L41-L57 ``` By default the app uses CometBFT app config templa...

(BY_DEFAULT_COMMA)


[style] ~123-~123: Consider a shorter alternative to avoid wordiness.
Context: ...saction requires some sort of signature in order to be valid, the signing command is necess...

(IN_ORDER_TO_PREMIUM)

docs/learn/advanced/08-events.md

[misspelling] ~57-~57: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...d'| Query all transactions containing a x/bankSend[ServiceMsg`](../../bui...

(EN_A_VS_AN)

docs/learn/advanced/09-telemetry.md

[uncategorized] ~22-~22: You might be missing the article “a” here.
Context: ...emitting and collecting metrics through simple [API](https://github.com/cosmos/cosmos-...

(AI_EN_LECTOR_MISSING_DETERMINER_A)

docs/learn/advanced/11-runtx_middleware.md

[uncategorized] ~50-~50: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ...y default, that panic would be recovered and an error message will be printed to log...

(COMMA_COMPOUND_SENTENCE_2)


[typographical] ~50-~50: It seems that a comma is missing.
Context: ...ill be printed to log. To override that behaviour we should register a custom RecoveryHan...

(IN_ORDER_TO_VB_COMMA)

🔇 Additional comments (11)
docs/learn/advanced/09-telemetry.md (1)

22-22: Version update looks good

The documentation link has been correctly updated to reference the latest SDK version (v0.52.0-beta.2), which aligns with the version updates across other documentation files in this PR.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~22-~22: You might be missing the article “a” here.
Context: ...emitting and collecting metrics through simple [API](https://github.com/cosmos/cosmos-...

(AI_EN_LECTOR_MISSING_DETERMINER_A)

docs/learn/advanced/08-events.md (4)

23-23: LGTM: URL reference update is accurate.

The updated URL correctly points to the latest SDK version and relevant proto file for events.


68-68: LGTM: Code references are up-to-date.

The code references have been correctly updated to point to the latest SDK version.

Also applies to: 76-76


79-80: LGTM: Documentation updates improve clarity.

The added clarification about preferred event emission methods and deprecation notice is helpful for developers.

Also applies to: 83-83


88-88: LGTM: Code example effectively demonstrates typed events.

The reference provides a clear, real-world example of typed event usage from the group keeper implementation.

docs/learn/advanced/06-grpc_rest.md (3)

29-29: LGTM: Correct relative link to encoding documentation

The reference to the encoding documentation is properly formatted and correctly uses a relative path.


69-69: Please verify the line numbers in the Protobuf reference

The version update to v0.52.0-beta.2 is correct, but please verify that the line numbers #L23-L30 still point to the correct Protobuf query definition in the referenced file.

✅ Verification successful

Line numbers in the Protobuf reference are correct

The line numbers #L23-L30 correctly point to the AllBalances query definition in the bank module's Protobuf file. The referenced section shows the complete RPC definition including its documentation and HTTP endpoint configuration.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify the line numbers in the referenced proto file
gh api repos/cosmos/cosmos-sdk/contents/x/bank/proto/cosmos/bank/v1beta1/query.proto?ref=v0.52.0-beta.2 | jq -r '.content' | base64 -d | sed -n '23,30p'

Length of output: 226


Script:

#!/bin/bash
# Try using curl to fetch the raw content directly
curl -s "https://raw.githubusercontent.com/cosmos/cosmos-sdk/v0.52.0-beta.2/x/bank/proto/cosmos/bank/v1beta1/query.proto" | sed -n '23,30p'

Length of output: 578


34-34: Please verify the line numbers in the code reference

The version update to v0.52.0-beta.2 is correct, but please verify that the line numbers #L45-L47 still point to the correct code segment in the referenced file.

✅ Verification successful

Line numbers in the GitHub reference are correct

The line numbers #L45-L47 in the reference link correctly point to the RegisterTxService code segment in the v0.52.0-beta.2 version of server/types/app.go. The referenced lines contain the documentation and function signature for gRPC Query service registration.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify the line numbers in the referenced file
gh api repos/cosmos/cosmos-sdk/contents/server/types/app.go?ref=v0.52.0-beta.2 | jq -r '.content' | base64 -d | sed -n '45,47p'

Length of output: 201


Script:

#!/bin/bash
# Try a different approach to verify the content using curl
curl -s -L "https://raw.githubusercontent.com/cosmos/cosmos-sdk/v0.52.0-beta.2/server/types/app.go" | sed -n '45,47p'

Length of output: 269

docs/learn/advanced/07-cli.md (1)

46-46: Version references are correctly updated

All code references have been consistently updated to v0.52.0-beta.2, maintaining documentation accuracy.

Also applies to: 60-60, 62-62, 69-69, 82-82, 88-88, 94-94, 102-102, 108-108, 118-118, 130-130, 143-143, 157-157

docs/learn/advanced/00-baseapp.md (2)

Line range hint 1-1028: Documentation quality is excellent

The documentation is well-written, clear, and maintains a professional tone throughout. The explanations of complex concepts are thorough and accessible.


Line range hint 1-1028: Documentation structure and references are well-organized

The documentation maintains excellent cross-referencing and linking between related concepts, making it easy to navigate and understand the relationships between different components.

docs/learn/advanced/09-telemetry.md Outdated Show resolved Hide resolved
docs/learn/advanced/08-events.md Outdated Show resolved Hide resolved
docs/learn/advanced/05-encoding.md Show resolved Hide resolved
docs/learn/advanced/00-baseapp.md Show resolved Hide resolved
@@ -34,14 +34,14 @@ tree.

For storage encoding, module developers are encouraged to use Protobuf encoding for their types
but may choose any encoding schema they like. The
[collections](../../build/packages/02-collections.md) package automatically handles encoding and
[collections](https://github.com/cosmos/cosmos-sdk/blob/collections/v0.4.0/collections/README.md) package automatically handles encoding and
Copy link
Member

Choose a reason for hiding this comment

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

when the docs build script this gets fixed, it can be reverted.

Copy link
Member

Choose a reason for hiding this comment

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

is it broken?

Copy link
Member

Choose a reason for hiding this comment

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

it should work and resolve this

Copy link
Member

Choose a reason for hiding this comment

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

yes

Copy link
Member

@tac0turtle tac0turtle left a comment

Choose a reason for hiding this comment

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

ACK, need to revert two url changes to avoid breakage on the site

| `tx.height=23` | Query all transactions at height 23 |
| `message.action='/cosmos.bank.v1beta1.Msg/Send'` | Query all transactions containing an x/bank `Send` [Service `Msg`](../../build/building-modules/03-msg-services.md). Note the `'`s around the value. |
| `message.module='bank'` | Query all transactions containing messages from the x/bank module. Note the `'`s around the value. |
| `create_validator.validator='cosmosval1...'` | x/staking-specific Event, see [x/staking SPEC](../../../x/staking/README.md#events). |
Copy link
Member

Choose a reason for hiding this comment

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

ditto

Copy link
Member

Choose a reason for hiding this comment

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

yeah this should be reverted, it will resolve on the website, but not on here

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.

lgtm!, but could you revert the two links @tac0turtle pointed out?

| `tx.height=23` | Query all transactions at height 23 |
| `message.action='/cosmos.bank.v1beta1.Msg/Send'` | Query all transactions containing an x/bank `Send` [Service `Msg`](../../build/building-modules/03-msg-services.md). Note the `'`s around the value. |
| `message.module='bank'` | Query all transactions containing messages from the x/bank module. Note the `'`s around the value. |
| `create_validator.validator='cosmosval1...'` | x/staking-specific Event, see [x/staking SPEC](../../../x/staking/README.md#events). |
Copy link
Member

Choose a reason for hiding this comment

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

yeah this should be reverted, it will resolve on the website, but not on here

@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Oct 25, 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 and nitpick comments (3)
docs/learn/advanced/11-runtx_middleware.md (1)

50-50: Consider improving sentence structure with proper punctuation

The sentence could be clearer with better punctuation:

-By default, that panic would be recovered and an error message will be printed to log.
+By default, that panic would be recovered, and an error message will be printed to the log.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~50-~50: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ...y default, that panic would be recovered and an error message will be printed to log...

(COMMA_COMPOUND_SENTENCE_2)


[typographical] ~50-~50: It seems that a comma is missing.
Context: ...ill be printed to log. To override that behaviour we should register a custom RecoveryHan...

(IN_ORDER_TO_VB_COMMA)

docs/learn/advanced/05-encoding.md (2)

40-43: Consider enhancing interface documentation.

The explanation of BinaryCodec and JSONCodec interfaces could be more detailed. Consider adding:

  • Concrete examples of when each interface is used
  • The relationship between these interfaces
  • Common implementation patterns

Would you like me to help draft the additional documentation?


146-146: Consider rephrasing for American English style.

Consider changing "Have a look at" to "Take a look at" to align with American English conventions.

🧰 Tools
🪛 LanguageTool

[locale-violation] ~146-~146: In American English, “take a look” is more commonly used.
Context: ...face` method to bundle these two steps. Have a look at [a real-life example in the x/auth m...

(HAVE_A_LOOK)

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 4916e66 and b7d71cf.

📒 Files selected for processing (3)
  • docs/learn/advanced/05-encoding.md (6 hunks)
  • docs/learn/advanced/08-events.md (3 hunks)
  • docs/learn/advanced/11-runtx_middleware.md (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/learn/advanced/08-events.md
🧰 Additional context used
📓 Path-based instructions (2)
docs/learn/advanced/05-encoding.md (1)

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

docs/learn/advanced/11-runtx_middleware.md (1)

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

🪛 LanguageTool
docs/learn/advanced/05-encoding.md

[locale-violation] ~146-~146: In American English, “take a look” is more commonly used.
Context: ...face` method to bundle these two steps. Have a look at [a real-life example in the x/auth m...

(HAVE_A_LOOK)

docs/learn/advanced/11-runtx_middleware.md

[uncategorized] ~50-~50: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ...y default, that panic would be recovered and an error message will be printed to log...

(COMMA_COMPOUND_SENTENCE_2)


[typographical] ~50-~50: It seems that a comma is missing.
Context: ...ill be printed to log. To override that behaviour we should register a custom RecoveryHan...

(IN_ORDER_TO_VB_COMMA)

🔇 Additional comments (4)
docs/learn/advanced/11-runtx_middleware.md (4)

11-11: LGTM: Version reference correctly updated

The version update to v0.52.0-beta.2 is consistent with the documentation updates across the SDK.


16-16: LGTM: Interface reference link updated

The version in the code reference link is correctly updated to match the SDK version.


36-36: LGTM: Correct use of contraction

The grammatical correction from "Lets" to "Let's" is appropriate.


28-30: LGTM: Code reference link updated correctly

The version update in the code reference link maintains consistency with the SDK version.

✅ Verification successful

Code reference link and line numbers are accurate

The referenced code at lines 549-554 in baseapp/baseapp.go correctly points to the AddRunTxRecoveryHandler function implementation in the v0.52.0-beta.2 version of cosmos-sdk.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify that the referenced line numbers point to the correct code
gh api repos/cosmos/cosmos-sdk/contents/baseapp/baseapp.go?ref=v0.52.0-beta.2 | jq -r '.content' | base64 -d | sed -n '549,554p'

Length of output: 202


Script:

#!/bin/bash
# Try alternative approach to fetch and verify the content
curl -s -L "https://raw.githubusercontent.com/cosmos/cosmos-sdk/v0.52.0-beta.2/baseapp/baseapp.go" | sed -n '549,554p'

Length of output: 384

@julienrbrt julienrbrt added this pull request to the merge queue Oct 25, 2024
Merged via the queue into main with commit 9f79dd3 Oct 25, 2024
70 of 71 checks passed
@julienrbrt julienrbrt deleted the julian/learn-advance-0.52 branch October 25, 2024 15:08
mergify bot pushed a commit that referenced this pull request Oct 25, 2024
(cherry picked from commit 9f79dd3)
@mergify mergify bot mentioned this pull request Oct 25, 2024
12 tasks
julienrbrt pushed a commit that referenced this pull request Oct 25, 2024
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants