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: remove duplicate sentence in RFC 003 #23506

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

wonderfan
Copy link
Contributor

@wonderfan wonderfan commented Jan 25, 2025

The sentence "Recently we have identified the following key target user groups:" was accidentally repeated. This commit removes the duplicate to improve readability.

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, 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
    • Updated RFC-003 to clarify target user groups for the Cosmos SDK.
    • Refined description of user groups with more precise language.
    • Highlighted distinctions between single-language and multi-language project needs.
    • Corrected typographical error in the "State and Volatility" section.

@wonderfan wonderfan requested a review from a team as a code owner January 25, 2025 00:07
Copy link
Contributor

coderabbitai bot commented Jan 25, 2025

📝 Walkthrough

Walkthrough

The pull request updates the RFC-003 document by enhancing the "Background" section to provide a clearer description of the key target user groups for the Cosmos SDK. It distinguishes between two user groups: one focusing on projects that target a single programming language and another on those integrating multiple languages and environments. Additionally, a typographical error in the "State and Volatility" section is corrected. The overall structure of the document remains unchanged.

Changes

File Change Summary
docs/rfc/rfc-003-crosslang.md Enhanced description of two distinct target user groups in the Background section; corrected "radonly" to "readonly" in the State and Volatility section.

Suggested Reviewers

  • julienrbrt
  • tac0turtle
  • akhilkumarpilli

Possibly related PRs

Suggested labels

Type: ADR


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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

@wonderfan wonderfan changed the title ix: remove duplicate sentence in RFC 003 fix: remove duplicate sentence in RFC 003 Jan 25, 2025
@wonderfan wonderfan changed the title fix: remove duplicate sentence in RFC 003 docs: remove duplicate sentence in RFC 003 Jan 25, 2025
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

🧹 Nitpick comments (1)
docs/rfc/rfc-003-crosslang.md (1)

173-173: Add blank lines around the list for better formatting.

To improve markdown formatting and readability, add blank lines before and after the bullet point list.

Apply this formatting change:

 **Volatility** describes a message handler's behavior with respect to state and side effects.
 It is an enum value that can have one of the following values:
+
* `volatile`: the handler can have side effects and send `volatile`, `readonly` or `pure` messages to other accounts. Such handlers are expected to both read and write state.
* `readonly`: the handler cannot cause effects side effects and can only send `readonly` or `pure` messages to other accounts. Such handlers are expected to only read state.
* `pure`: the handler cannot cause any side effects and can only call other pure handlers. Such handlers are expected to neither read nor write state.
+
The hypervisor will enforce **volatility** rules when routing messages to account handlers.
🧰 Tools
🪛 Markdownlint (0.37.0)

173-173: null
Lists should be surrounded by blank lines

(MD032, blanks-around-lists)

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d58d5da and f49b9bb.

📒 Files selected for processing (1)
  • docs/rfc/rfc-003-crosslang.md (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/rfc/rfc-003-crosslang.md (1)

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

🪛 Markdownlint (0.37.0)
docs/rfc/rfc-003-crosslang.md

173-173: null
Lists should be surrounded by blank lines

(MD032, blanks-around-lists)

⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: repo-analysis
  • GitHub Check: build (arm64)
  • GitHub Check: build (amd64)
  • GitHub Check: markdown-link-check
  • GitHub Check: dependency-review
  • GitHub Check: Summary
🔇 Additional comments (2)
docs/rfc/rfc-003-crosslang.md (2)

12-12: LGTM! Improved document readability.

The removal of the duplicate sentence "Recently we have identified the following key target user groups:" enhances the document's clarity while maintaining the intended meaning.


173-173: LGTM! Correct terminology used.

The description of the volatile handler type is accurate and consistent with the overall volatility model described in this section.

🧰 Tools
🪛 Markdownlint (0.37.0)

173-173: null
Lists should be surrounded by blank lines

(MD032, blanks-around-lists)

The sentence "Recently we have identified the following key target user groups:" was accidentally repeated. This commit removes the duplicate to improve readability.
It should be readonly instead of "radonly"
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

🧹 Nitpick comments (1)
docs/rfc/rfc-003-crosslang.md (1)

173-175: Add blank lines around the list for better readability.

Following markdown best practices, lists should be surrounded by blank lines to improve readability and ensure consistent rendering across different markdown processors.

Apply this formatting change:

**Volatility** describes a message handler's behavior with respect to state and side effects.
It is an enum value that can have one of the following values:
+
* `volatile`: the handler can have side effects and send `volatile`, `readonly` or `pure` messages to other accounts. Such handlers are expected to both read and write state.
* `readonly`: the handler cannot cause effects side effects and can only send `readonly` or `pure` messages to other accounts. Such handlers are expected to only read state.
* `pure`: the handler cannot cause any side effects and can only call other pure handlers. Such handlers are expected to neither read nor write state.
+
The hypervisor will enforce **volatility** rules when routing messages to account handlers.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~174-~174: Loose punctuation mark.
Context: ... both read and write state. * readonly: the handler cannot cause effects side e...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~175-~175: Loose punctuation mark.
Context: ...re expected to only read state. * pure: the handler cannot cause any side effec...

(UNLIKELY_OPENING_PUNCTUATION)

🪛 Markdownlint (0.37.0)

173-173: null
Lists should be surrounded by blank lines

(MD032, blanks-around-lists)

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f49b9bb and 512dad4.

📒 Files selected for processing (1)
  • docs/rfc/rfc-003-crosslang.md (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/rfc/rfc-003-crosslang.md (1)

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

🪛 Markdownlint (0.37.0)
docs/rfc/rfc-003-crosslang.md

173-173: null
Lists should be surrounded by blank lines

(MD032, blanks-around-lists)

⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: tests (03)
  • GitHub Check: build (arm64)
  • GitHub Check: build (amd64)
  • GitHub Check: markdown-link-check
  • GitHub Check: dependency-review
  • GitHub Check: Summary
🔇 Additional comments (1)
docs/rfc/rfc-003-crosslang.md (1)

12-12: LGTM! Improved document readability.

The removal of the duplicate sentence "Recently we have identified the following key target user groups:" enhances the document's clarity while maintaining its meaning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant