feat(synapse-interface): create template event maintenance components, remove ecotone + metis event maintenance components

[bigboydiamonds]

Summary by CodeRabbit

• New Features

  • Simplified and optimized the structure and styling of the Announcement Banner component.
  • Introduced functionality for creating automated announcement banners and event countdown timer bars for the Ecotone Fork Upgrade event.

• Refactor

  • Reorganized import paths and adjusted logic in Ecotone Fork Upgrade components for better clarity.
  • Simplified the State Managed Bridge component by removing outdated functionalities.

• Chores

  • Removed the Ecotone Fork UpgradeBanner component from the Home page.

a365f5cc46a04fe4751561d5755fa27fc16e6649: synapse-interface preview link
401fc705612a293014cd38336a15b85090de28a5: synapse-interface preview link
6fb7d1bfa06095bccbc581e85c8dcaabf0e17fa0: synapse-interface preview link
cd288c867af17ff2da5883ede161793e32c58b6a: synapse-interface preview link
3ce2c9d98340d884b3f55b2514a745033090bc56: synapse-interface preview link
e034def0bdbddc8e07d5e84af6e5bcd7fba4a14a: synapse-interface preview link
07e1598190a3fb2a731a33445a3dfafdfda0761a: synapse-interface preview link
dd7a018cd8075ab1fcd8329596306394f012ea10: synapse-interface preview link

[coderabbitai]

Walkthrough

The changes revolve around enhancing a countdown progress bar component, reorganizing import paths, introducing a new hook for an upgrade countdown, and simplifying page components by removing specific upgrade countdown and warning elements. These modifications aim to improve user experience and streamline code maintenance.

Changes

Files	Summary
.../Maintenance/AnnouncementBanner.tsx	Updated to simplify structure and styling.
.../Maintenance/Events/example/EcotoneForkUpgrade.tsx	Introduced functionality for automated announcement banners and event countdown timer bars related to Ecotone Fork Upgrade.
.../pages/index.tsx	Removed EcotoneForkUpgradeBanner component from the Home component.

🐇✨
In the land of code, where the synapses leap,
Changes abound, through the files, they seep.
Countdowns enhanced, with care and with glee,
Simplification's key, as clear as can be.
So here's to the changes, may they serve you right,
A hop, skip, and jump, into the code's light.
🌟🐾

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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-tests 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 tests 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 tests.
  • @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.
• The JSON schema for the configuration file is available here.
• 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

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[cloudflare-workers-and-pages]

Deploying sanguine-fe with    Cloudflare Pages

Latest commit:	a428e1c
Status:	✅  Deploy successful!
Preview URL:	https://f59738ea.sanguine-fe.pages.dev
Branch Preview URL:	https://fe-remove-upgrade-annoucemen.sanguine-fe.pages.dev

View logs

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 5c3dc59 and 6ade432.

Files selected for processing (4)

• packages/synapse-interface/components/Maintenance/EventCountdownProgressBar.tsx (2 hunks)
• packages/synapse-interface/components/Maintenance/Events/example/EcotoneForkUpgrade.tsx (2 hunks)
• packages/synapse-interface/pages/index.tsx (2 hunks)
• packages/synapse-interface/pages/state-managed-bridge/index.tsx (5 hunks)

Additional comments: 6

packages/synapse-interface/pages/index.tsx (1)

• 3-8: > 📝 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 EcotoneForkUpgradeBanner and MetisDowntimeBanner components from the Home component has been successfully executed. Ensure that any associated state management, styles, or other dependencies specific to these components are also cleaned up if no longer needed.

packages/synapse-interface/components/Maintenance/Events/example/EcotoneForkUpgrade.tsx (3)

• 1-16: Reorganization of import paths and the addition of explanatory comments enhance the file's readability and maintainability. Good practice to provide context for future developers.
• 1-19: > 📝 NOTE

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

The implementation of EcotoneForkUpgradeBanner and EcotoneForkWarningMessage components demonstrates correct use of hooks and conditional rendering based on the Ecotone Fork Upgrade event's timing and chain IDs. Well-structured and logical.

• 77-84: The introduction of the useEcotoneForkCountdownProgress hook effectively manages the countdown progress for the Ecotone Fork Upgrade. The use of conditional logic based on chain IDs and event status is well-implemented.

packages/synapse-interface/components/Maintenance/EventCountdownProgressBar.tsx (1)

• 4-12: Enhancements to the useEventCountdownProgressBar function, including additional parameters for event labeling, start and end dates, and a completion status flag, significantly improve the function's flexibility and usability. The detailed documentation and logical implementation of new features are commendable.

packages/synapse-interface/pages/state-managed-bridge/index.tsx (1)

• 85-90: > 📝 NOTE

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

The simplification of the StateManagedBridge component's logic, through the careful removal of specific event maintenance components and their associated logic, aligns with best practices for maintainability and scalability. Ensure that any associated hooks or utilities no longer needed due to these removals are also cleaned up if applicable.

[cloudflare-workers-and-pages]

Deploying sanguine with    Cloudflare Pages

Latest commit:	a428e1c
Status:	✅  Deploy successful!
Preview URL:	https://2fe73f2a.sanguine.pages.dev
Branch Preview URL:	https://fe-remove-upgrade-annoucemen.sanguine.pages.dev

View logs

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 6ade432 and 7ad2a5c.

Files selected for processing (1)

• packages/synapse-interface/components/Maintenance/Events/example/EcotoneForkUpgrade.tsx (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• packages/synapse-interface/components/Maintenance/Events/example/EcotoneForkUpgrade.tsx

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 7ad2a5c and 40e4aa8.

Files selected for processing (1)

• packages/synapse-interface/components/Maintenance/Events/example/EcotoneForkUpgrade.tsx (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• packages/synapse-interface/components/Maintenance/Events/example/EcotoneForkUpgrade.tsx

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 40e4aa8 and 963249d.

Files selected for processing (1)

• packages/synapse-interface/components/Maintenance/Events/example/EcotoneForkUpgrade.tsx (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• packages/synapse-interface/components/Maintenance/Events/example/EcotoneForkUpgrade.tsx

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 963249d and a428e1c.

Files selected for processing (3)

• packages/synapse-interface/components/Maintenance/AnnouncementBanner.tsx (1 hunks)
• packages/synapse-interface/components/Maintenance/Events/example/EcotoneForkUpgrade.tsx (1 hunks)
• packages/synapse-interface/pages/index.tsx (2 hunks)

Files skipped from review as they are similar to previous changes (2)

• packages/synapse-interface/components/Maintenance/Events/example/EcotoneForkUpgrade.tsx
• packages/synapse-interface/pages/index.tsx

Additional comments: 4

packages/synapse-interface/components/Maintenance/AnnouncementBanner.tsx (4)

• 57-57: The use of gradient backgrounds (bg-gradient-to-r from-fuchsia-600/25 to-purple-600/25) adds a modern and visually appealing aspect to the banner. However, ensure that this color scheme aligns with the overall design system and accessibility standards of your application.
• 60-60: The max-w-[1111px] style sets a maximum width for the banner, which is good for ensuring that the content does not stretch too wide on larger screens. Consider verifying if this specific value aligns with the design guidelines of your application or if it should be adjusted to match other components.
• 63-63: It's great to see dynamic content ({bannerContents}) being used within the banner, allowing for flexibility in what is displayed. Ensure that the content passed as bannerContents is sanitized or safely handled to prevent any potential security risks, such as XSS attacks.
• 66-66: The button styling and the inclusion of an SVG for the close icon are well-implemented. However, consider adding a focus state for accessibility purposes, ensuring that users navigating with keyboards have a clear indication of the button's focus.