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

Submitter: remove IsL2 param #2442

Merged
merged 1 commit into from
Apr 6, 2024
Merged

Submitter: remove IsL2 param #2442

merged 1 commit into from
Apr 6, 2024

Conversation

dwasse
Copy link
Collaborator

@dwasse dwasse commented Apr 3, 2024

Description
Removes an unused parameter from the submitter config.

Metadata

Summary by CodeRabbit

  • Refactor
    • Updated chain configuration logic to enhance clarity and efficiency in identifying blockchain layers.

@dwasse dwasse requested a review from trajan0x as a code owner April 3, 2024 20:45
Copy link
Contributor

coderabbitai bot commented Apr 3, 2024

Walkthrough

The recent update involves the removal of the IsL2 field and its associated method from several components within the configuration setup of the ethergo project. Specifically, the ChainConfig struct, the Config type, and the IConfig interface no longer accommodate logic to distinguish L2 (Layer 2) chains. This simplification could affect how the system identifies and interacts with different blockchain layers.

Changes

Files Change Summary
.../submitter/config/config.go, .../config/iconfig_generated.go Removed IsL2 field and related method from ChainConfig, Config, and IConfig.

🎉🐰✨
In the world of code, where changes are bold,
A rabbit hopped in, a story to be told.
"No more 'IsL2', no layers to see,
Just simpler code, as happy as can be."
With every hop, the code did change,
In the ethergo land, wide and strange.
🌟🐇✨

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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/coderabbit-overrides.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

codecov bot commented Apr 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 46.89876%. Comparing base (17cbd4f) to head (9da1f3a).
Report is 1 commits behind head on master.

Additional details and impacted files
@@                 Coverage Diff                 @@
##              master       #2442         +/-   ##
===================================================
- Coverage   46.92720%   46.89876%   -0.02844%     
===================================================
  Files            383         400         +17     
  Lines          29273       30649       +1376     
  Branches          83          83                 
===================================================
+ Hits           13737       14374        +637     
- Misses         14073       14740        +667     
- Partials        1463        1535         +72     
Flag Coverage Δ
cctp-relayer 43.53414% <ø> (?)
committee 62.90550% <ø> (-0.84626%) ⬇️
omnirpc 53.23194% <ø> (ø)
promexporter 75.91241% <ø> (?)
rfq 28.97609% <ø> (ø)
sin-executor 61.57635% <ø> (ø)
stiprelayer 3.33333% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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

Review Status

Configuration used: .coderabbit.yaml

Commits Files that changed from the base of the PR and between b99604b and 9da1f3a.
Files selected for processing (2)
  • ethergo/submitter/config/config.go (2 hunks)
  • ethergo/submitter/config/iconfig_generated.go (1 hunks)
Additional comments not posted (3)
ethergo/submitter/config/iconfig_generated.go (1)

20-25: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [1-33]

The removal of the IsL2 method from the IConfig interface aligns with the PR's objectives and does not introduce inconsistencies. However, consider addressing the existing TODO comments in a separate task to enhance the codebase's test coverage and reliability.

Would you like assistance in creating a GitHub issue to track the task of adding tests for the methods indicated by the TODO comments?

ethergo/submitter/config/config.go (2)

38-43: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [9-13]

The changes to the Config struct are consistent with the PR's objectives and do not introduce any inconsistencies. The documentation and structure remain clear and relevant.


38-43: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [22-34]

The changes to the ChainConfig struct align with the PR's objectives, removing the IsL2 field without affecting the struct's clarity or purpose. The documentation and fields are well-structured and relevant.

Copy link

Deploying sanguine-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: 9da1f3a
Status: ✅  Deploy successful!
Preview URL: https://e182ade2.sanguine-fe.pages.dev
Branch Preview URL: https://feat-no-l2.sanguine-fe.pages.dev

View logs

@aureliusbtc aureliusbtc merged commit 3964639 into master Apr 6, 2024
43 of 45 checks passed
@aureliusbtc aureliusbtc deleted the feat/no-l2 branch April 6, 2024 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants