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

fix: foundry test #1865

Closed
wants to merge 1 commit into from
Closed

fix: foundry test #1865

wants to merge 1 commit into from

Conversation

unknownunknown1
Copy link
Contributor

@unknownunknown1 unknownunknown1 commented Jan 28, 2025

PR-Codex overview

This PR focuses on updating the KlerosCoreTest contract to use the DisputeKitClassicBase instead of DisputeKitClassic for various emitted events and imports. It also imports IArbitratorV2 from a different source.

Detailed summary

  • Updated imports to use IArbitratorV2 from KlerosCoreBase.sol.
  • Changed emitted events from DisputeKitClassic to DisputeKitClassicBase in multiple instances:
    • DisputeCreation
    • CommitCast
    • Contribution
    • ChoiceFunded
    • Withdrawal
  • Adjusted the contract's event emissions accordingly.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

  • Refactor
    • Updated import statements for dispute kit interfaces and base classes
    • Modified event emissions to reference base classes in test file

Copy link
Contributor

coderabbitai bot commented Jan 28, 2025

Walkthrough

The changes involve modifications to the KlerosCore.t.sol test file, primarily focusing on import statements and event emissions. The modifications suggest a restructuring of the codebase, with import sources being updated and event references shifted from DisputeKitClassic to DisputeKitClassicBase. These changes appear to be part of a broader refactoring effort to consolidate and reorganize the dispute kit implementation and its associated test suite.

Changes

File Change Summary
contracts/test/foundry/KlerosCore.t.sol - Updated import statements for IArbitratorV2 and DisputeKitClassic
- Modified event emissions to reference DisputeKitClassicBase instead of DisputeKitClassic

Poem

🐰 In the realm of code, a rabbit's delight,
Imports shift and events take flight
From Classic to Base, a subtle dance
Refactoring magic, a testing romance
Kleros evolves with each gentle hop! 🧪


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 227337b and b6c5fb6.

📒 Files selected for processing (1)
  • contracts/test/foundry/KlerosCore.t.sol (8 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (15)
  • GitHub Check: Redirect rules - kleros-v2-testnet-devtools
  • GitHub Check: Redirect rules - kleros-v2-neo
  • GitHub Check: Header rules - kleros-v2-neo
  • GitHub Check: Header rules - kleros-v2-testnet-devtools
  • GitHub Check: Pages changed - kleros-v2-neo
  • GitHub Check: Pages changed - kleros-v2-testnet-devtools
  • GitHub Check: Redirect rules - kleros-v2-testnet
  • GitHub Check: Redirect rules - kleros-v2-testnet
  • GitHub Check: Header rules - kleros-v2-testnet
  • GitHub Check: Header rules - kleros-v2-testnet
  • GitHub Check: Pages changed - kleros-v2-testnet
  • GitHub Check: Pages changed - kleros-v2-testnet
  • GitHub Check: SonarCloud
  • GitHub Check: contracts-testing
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (3)
contracts/test/foundry/KlerosCore.t.sol (3)

1330-1330: Event emission updated to use DisputeKitClassicBase.

The event emission has been correctly updated to use DisputeKitClassicBase.DisputeCreation instead of DisputeKitClassic.DisputeCreation, aligning with the architectural changes.


1596-1596: Event emissions updated to use DisputeKitClassicBase in commit tests.

Both event emissions have been correctly updated to use DisputeKitClassicBase.CommitCast instead of DisputeKitClassic.CommitCast, maintaining consistency with the architectural changes.

Also applies to: 1612-1612


2696-2696: Event emissions updated to use DisputeKitClassicBase in withdrawal tests.

Both event emissions have been correctly updated to use DisputeKitClassicBase.Withdrawal instead of DisputeKitClassic.Withdrawal, completing the migration to the new base contract.

Also applies to: 2700-2700


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 or @coderabbitai title anywhere in the PR title to generate the title automatically.

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

netlify bot commented Jan 28, 2025

Deploy Preview for kleros-v2-testnet ready!

Name Link
🔨 Latest commit b6c5fb6
🔍 Latest deploy log https://app.netlify.com/sites/kleros-v2-testnet/deploys/67992bc01a46580008ac5faf
😎 Deploy Preview https://deploy-preview-1865--kleros-v2-testnet.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

netlify bot commented Jan 28, 2025

Deploy Preview for kleros-v2-neo ready!

Name Link
🔨 Latest commit b6c5fb6
🔍 Latest deploy log https://app.netlify.com/sites/kleros-v2-neo/deploys/67992bc06c48090008485781
😎 Deploy Preview https://deploy-preview-1865--kleros-v2-neo.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

netlify bot commented Jan 28, 2025

Deploy Preview for kleros-v2-testnet-devtools ready!

Name Link
🔨 Latest commit b6c5fb6
🔍 Latest deploy log https://app.netlify.com/sites/kleros-v2-testnet-devtools/deploys/67992bc06c75120008b7cfcd
😎 Deploy Preview https://deploy-preview-1865--kleros-v2-testnet-devtools.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

codeclimate bot commented Jan 28, 2025

Code Climate has analyzed commit b6c5fb6 and detected 0 issues on this pull request.

View more on Code Climate.

Copy link

netlify bot commented Jan 28, 2025

Deploy Preview for kleros-v2-university ready!

Name Link
🔨 Latest commit b6c5fb6
🔍 Latest deploy log https://app.netlify.com/sites/kleros-v2-university/deploys/67992bc092ca8500080b257c
😎 Deploy Preview https://deploy-preview-1865--kleros-v2-university.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@unknownunknown1
Copy link
Contributor Author

fixed in #1872

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