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: Update rollapp genesis docs #260

Merged
merged 2 commits into from
Jun 19, 2024

Conversation

hoangdv2429
Copy link
Contributor

@hoangdv2429 hoangdv2429 commented Jun 17, 2024

Summary by CodeRabbit

  • Tests
    • Improved test coverage for token transfer scenarios between a hub and a rollapp.
    • Updated descriptions, pre-conditions, and expected results for transfer tests to enhance clarity and accuracy.

Copy link
Contributor

coderabbitai bot commented Jun 17, 2024

Walkthrough

The changes are focused on testing scenarios for transferring tokens between a hub and a rollapp both pre- and post-genesis events. Adjustments include updates to test descriptions, pre-conditions, and expected results in the rollapp_genesis.md documentation and modifications to test functions in the rollapp_genesis_event_test.go file.

Changes

Files Change Summaries
tests_spec/rollapp_genesis.md Updated test descriptions, pre-conditions, and expected results for various token transfer scenarios.
.../rollapp_genesis_event_test.go Renamed and repositioned several test functions related to token transfer events for clarity and organization.

Sequence Diagram(s)

None required; changes are primarily descriptive and organizational.

Possibly related issues

Poem

In a world of hubs and rolls,
Tokens transfer, reach their goals,
Through events and genesis sight,
Pathways lit up bright.
Testing flows in coded prose,
Bugs and flaws now we expose,
With every go test that we write.
🐇✨


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

@hoangdv2429 hoangdv2429 marked this pull request as ready for review June 18, 2024 09:44
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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 21908ad and 3d9d5c0.

Files selected for processing (1)
  • tests_spec/rollapp_genesis.md (1 hunks)
Additional context used
LanguageTool
tests_spec/rollapp_genesis.md

[uncategorized] ~5-~5: The abbreviation “i.e.” (= that is) requires two periods. (I_E)
Context: .../li>

  • VFC should be created on hub (i.e erc20)
  • Rollapp tokens with r...

  • Additional comments not posted (5)
    tests_spec/rollapp_genesis.md (5)

    5-5: This detailed update enhances clarity and aligns well with the linked test case.

    Tools
    LanguageTool

    [uncategorized] ~5-~5: The abbreviation “i.e.” (= that is) requires two periods. (I_E)
    Context: .../li>

  • VFC should be created on hub (i.e erc20)
  • Rollapp tokens with r...


  • 7-7: The updates provide clear and detailed information about the test scenario, including links to both EVM and Wasm test implementations.


    9-9: The scenario is well-described, highlighting the failure conditions effectively. The links to the test cases are accurate.


    11-11: The description is thorough, detailing both the scenario and the expected failure conditions, with accurate links to the test cases.


    12-12: The scenario is clearly described, including the expected failure conditions, and the links to the test cases are correctly updated.

    @@ -2,11 +2,11 @@

    | No | Scenario | Pre-condition | Pre-condition check | Expected result | Expected result check | Covered By |
    |----|----------|---------------|---------------------|-----------------|-----------------------|------------|
    | 1 | Rollapp genesis tokens on the hub upon channel creation | <ul> <li> Create relevant genesis accounts and metadata info </li> <li> Upon channel creation, trigger genesis events in both rollapp and hub (special tx) </li> </ul> | ✅ | <ul> <li> denometadata should be created </li> <li> VFC should be created on hub (i.e erc20) </li> <li> Rollapp tokens with relevant amount should be locked on the rollapp </li> <li> genesis accounts should have the relevant balance on the hub </li> </ul> | ✅ | [TestRollappGenesisEvent_EVM](../tests/rollapp_genesis_event_test.go#24) |
    | 1 | Rollapp genesis tokens on the hub upon channel creation | <ul> <li> Create relevant genesis accounts and metadata info </li> <li> Upon channel creation, trigger genesis events in both rollapp and hub (special tx) </li> </ul> | ✅ | <ul> <li> denometadata should be created </li> <li> VFC should be created on hub (i.e erc20) </li> <li> Rollapp tokens with relevant amount should be locked on the rollapp </li> <li> genesis accounts should have the relevant balance on the hub </li> </ul> | ✅ | [TestRollappGenesisEvent_EVM](../tests/rollapp_genesis_event_test.go#26) |
    Copy link
    Contributor

    Choose a reason for hiding this comment

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

    Correct the abbreviation for clarity.

    - VFC should be created on hub (i.e erc20)
    + VFC should be created on hub (i.e., erc20)
    Committable suggestion

    ‼️ IMPORTANT
    Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

    Suggested change
    | 1 | Rollapp genesis tokens on the hub upon channel creation | <ul> <li> Create relevant genesis accounts and metadata info </li> <li> Upon channel creation, trigger genesis events in both rollapp and hub (special tx) </li> </ul> || <ul> <li> denometadata should be created </li> <li> VFC should be created on hub (i.e erc20) </li> <li> Rollapp tokens with relevant amount should be locked on the rollapp </li> <li> genesis accounts should have the relevant balance on the hub </li> </ul> || [TestRollappGenesisEvent_EVM](../tests/rollapp_genesis_event_test.go#26) |
    | 1 | Rollapp genesis tokens on the hub upon channel creation | <ul> <li> Create relevant genesis accounts and metadata info </li> <li> Upon channel creation, trigger genesis events in both rollapp and hub (special tx) </li> </ul> || <ul> <li> denometadata should be created </li> <li> VFC should be created on hub (i.e., erc20) </li> <li> Rollapp tokens with relevant amount should be locked on the rollapp </li> <li> genesis accounts should have the relevant balance on the hub </li> </ul> || [TestRollappGenesisEvent_EVM](../tests/rollapp_genesis_event_test.go#26) |
    Tools
    LanguageTool

    [uncategorized] ~5-~5: The abbreviation “i.e.” (= that is) requires two periods. (I_E)
    Context: .../li>

  • VFC should be created on hub (i.e erc20)
  • Rollapp tokens with r...

  • @anhductn2001 anhductn2001 merged commit 24e1882 into main Jun 19, 2024
    @anhductn2001 anhductn2001 deleted the chore/update_rollapp_genesis_md branch June 19, 2024 04:19
    hoangdv2429 added a commit that referenced this pull request Jul 25, 2024
    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.

    2 participants