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: fix some comments #1517

Merged
merged 2 commits into from
Jul 22, 2024
Merged

chore: fix some comments #1517

merged 2 commits into from
Jul 22, 2024

Conversation

pudongair
Copy link
Contributor

@pudongair pudongair commented Jul 19, 2024

fix some comments

PR Checklist:

  • Have you read the CONTRIBUTING.md?
  • Does your PR follow the C4 patch requirements?
  • Have you rebased your work on top of the latest master?
  • Have you checked your code compiles? (make)
  • Have you included tests for any non-trivial functionality?
  • Have you checked your code passes the unit tests? (make test)
  • Have you checked your code formatting is correct? (go fmt)
  • Have you checked your basic code style is fine? (golangci-lint run)
  • If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
  • If your changes affect the client infrastructure, have you run the integration test?
  • If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
  • If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
  • If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

  • New Features

    • Updated the __CronosSendToIbc event to include a channelId argument, enhancing flexibility in token transfers.
  • Bug Fixes

    • Corrected typographical errors in various documentation and test files for improved clarity and professionalism.
  • Documentation

    • Improved accuracy and clarity in the README and architectural documentation.

@pudongair pudongair requested a review from a team as a code owner July 19, 2024 12:25
@pudongair pudongair requested review from yihuang and mmsqe and removed request for a team July 19, 2024 12:25
Copy link
Contributor

coderabbitai bot commented Jul 19, 2024

Walkthrough

The recent changes include a significant update to the __CronosSendToIbc event, which now incorporates a channelId argument, enhancing its functionality for IBC token transfers. Additionally, minor textual corrections were made across various documentation and test files to improve clarity and professionalism. These updates ensure both the code and accompanying documentation are polished and user-friendly.

Changes

Files Change Summary
docs/architecture/adr-007.md Updated signature of __CronosSendToIbc event to include channelId, enhancing IBC functionality.
docs/gravity-bridge/dev-setup-guide.md Corrected "succesfully" to "successfully."
integration_tests/test_basic.py Fixed spelling of "succesfully" to "successfully" in test outputs.
integration_tests/test_replay_block.py Corrected "succeds" to "succeeds" in comments for clarity.
memiavl/README.md Changed "random accessbility" to "random accessibility" for improved accuracy.
memiavl/multitree.go Corrected comment from "// clear the dirty informaton" to "// clear the dirty information."

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Cronos
    participant IBC

    User->>Cronos: Send tokens
    Cronos->>IBC: Transfer tokens with channelId
    IBC-->>Cronos: Confirmation of transfer
    Cronos-->>User: Tokens sent successfully
Loading

🐰 In a world where tokens roam,
A rabbit hops to bring them home.
With channels new and names so bright,
We celebrate our code's delight!
Fixes small, yet spirits high,
In the land of tech, we leap and fly! 🐇✨


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.

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)
docs/architecture/adr-007.md (1)

40-40: Fix unordered list style.

The list item should use an asterisk instead of a dash.

- - Event `__CronosSendToIbc` has different signature in CRC20 and CR21.
+ * Event `__CronosSendToIbc` has different signature in CRC20 and CR21.
Tools
Markdownlint

40-40: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

docs/gravity-bridge/dev-setup-guide.md (1)

168-168: Correct the grammar.

Change "setup" to "set up" to use the correct past participle form.

- the gravity bridge between ethereum and cronos is setup successfully.
+ the gravity bridge between ethereum and cronos is set up successfully.
Tools
LanguageTool

[grammar] ~168-~168: Make sure that the noun ‘setup’ is correct. Did you mean the past participle “set up”?
Context: ...y bridge between ethereum and cronos is setup successfully.

(BE_VB_OR_NN)

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7f581a6 and 833d1cc.

Files selected for processing (6)
  • docs/architecture/adr-007.md (1 hunks)
  • docs/gravity-bridge/dev-setup-guide.md (1 hunks)
  • integration_tests/test_basic.py (2 hunks)
  • integration_tests/test_replay_block.py (1 hunks)
  • memiavl/README.md (1 hunks)
  • memiavl/multitree.go (1 hunks)
Files skipped from review due to trivial changes (4)
  • integration_tests/test_basic.py
  • integration_tests/test_replay_block.py
  • memiavl/README.md
  • memiavl/multitree.go
Additional context used
Markdownlint
docs/architecture/adr-007.md

40-40: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

LanguageTool
docs/gravity-bridge/dev-setup-guide.md

[grammar] ~168-~168: Make sure that the noun ‘setup’ is correct. Did you mean the past participle “set up”?
Context: ...y bridge between ethereum and cronos is setup successfully.

(BE_VB_OR_NN)

@yihuang
Copy link
Collaborator

yihuang commented Jul 20, 2024

can you sign the commit @pudongair

Signed-off-by: pudongair <[email protected]>
@pudongair
Copy link
Contributor Author

can you sign the commit @pudongair

Signed~

Please review again.

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)
docs/architecture/adr-007.md (1)

40-40: Use asterisks for unordered list items.

The markdown linting tool suggests using an asterisk instead of a dash for unordered list items.

- - Event `__CronosSendToIbc` has different signature in CRC20 and CR21.
+ * Event `__CronosSendToIbc` has different signature in CRC20 and CR21.
Tools
Markdownlint

40-40: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

docs/gravity-bridge/dev-setup-guide.md (1)

168-168: Use "set up" instead of "setup".

The LanguageTool suggests using "set up" instead of "setup" to correct the grammatical issue.

- After all the orchestrator processes run, the gravity bridge between ethereum and cronos is setup successfully.
+ After all the orchestrator processes run, the gravity bridge between ethereum and cronos is set up successfully.
Tools
LanguageTool

[grammar] ~168-~168: Make sure that the noun ‘setup’ is correct. Did you mean the past participle “set up”?
Context: ...y bridge between ethereum and cronos is setup successfully.

(BE_VB_OR_NN)

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 833d1cc and 32822a6.

Files selected for processing (6)
  • docs/architecture/adr-007.md (1 hunks)
  • docs/gravity-bridge/dev-setup-guide.md (1 hunks)
  • integration_tests/test_basic.py (2 hunks)
  • integration_tests/test_replay_block.py (1 hunks)
  • memiavl/README.md (1 hunks)
  • memiavl/multitree.go (1 hunks)
Files skipped from review due to trivial changes (3)
  • integration_tests/test_basic.py
  • integration_tests/test_replay_block.py
  • memiavl/multitree.go
Files skipped from review as they are similar to previous changes (1)
  • memiavl/README.md
Additional context used
Markdownlint
docs/architecture/adr-007.md

40-40: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

LanguageTool
docs/gravity-bridge/dev-setup-guide.md

[grammar] ~168-~168: Make sure that the noun ‘setup’ is correct. Did you mean the past participle “set up”?
Context: ...y bridge between ethereum and cronos is setup successfully.

(BE_VB_OR_NN)

@yihuang yihuang enabled auto-merge July 22, 2024 05:05
Copy link

codecov bot commented Jul 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.84%. Comparing base (8384cad) to head (41fbf46).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1517   +/-   ##
=======================================
  Coverage   36.84%   36.84%           
=======================================
  Files         117      117           
  Lines        8124     8124           
=======================================
  Hits         2993     2993           
  Misses       4766     4766           
  Partials      365      365           
Files Coverage Δ
memiavl/multitree.go 76.01% <ø> (ø)

@yihuang yihuang added this pull request to the merge queue Jul 22, 2024
Merged via the queue into crypto-org-chain:main with commit 901d841 Jul 22, 2024
36 of 37 checks passed
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.

3 participants