8000 fix(bridge): fix progress bar background by shoom3301 · Pull Request #5888 · cowprotocol/cowswap · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix(bridge): fix progress bar background #5888

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

Merged
merged 1 commit into from
Jun 25, 2025
Merged

Conversation

shoom3301
Copy link
Collaborator
@shoom3301 shoom3301 commented Jun 25, 2025

Summary

Before:
telegram-cloud-photo-size-5-6260377316454680345-y

After:
image

To Test

The progress bar (bridge steps) background should look good both for light and dark themes

Summary by CodeRabbit

  • New Features

    • Introduced a theme configuration update step in the application interface.
  • Style

    • Updated background color styling to use a CSS variable for improved theme consistency.
  • Refactor

    • Added explicit return type annotations to several components for improved code clarity.
    • Removed unnecessary comments and ESLint disable statements.

@shoom3301 shoom3301 requested review from a team June 25, 2025 10:48
@shoom3301 shoom3301 self-assigned this Jun 25, 2025
Copy link
Contributor
coderabbitai bot commented Jun 25, 2025

Walkthrough

The changes introduce explicit return type annotations for several React components, update import statements, and adjust a styled component's background color to use a CSS variable. Additionally, a new theme configuration updater component is inserted into the application component tree, without affecting existing logic or control flow.

Changes

File(s) Change Summary
.../src/cosmos.decorator.tsx Added import and usage of ThemeConfigUpdater in the component tree.
.../src/modules/bridge/pure/CollapsibleBridgeRoute/index.tsx Added explicit return type ReactNode to component and void to internal function; removed ESLint comments.
.../src/modules/bridge/pure/ProgressDetails/index.tsx Added explicit return type ReactNode to component; removed TODOs and ESLint comments.
.../src/modules/orderProgressBar/pure/steps/BridgingStep.tsx Updated import to include UI; changed background color to CSS variable.

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant BlockNumberProvider
    participant ThemeConfigUpdater
    participant WalletUpdater

    App->>BlockNumberProvider: Render
    BlockNumberProvider->>ThemeConfigUpdater: Render as child
    ThemeConfigUpdater->>WalletUpdater: Render as sibling
Loading

Suggested reviewers

  • alfetopito
  • elena-zh

Poem

A hop and a skip, a theme update in place,
Types now explicit, no need to chase.
Colors from variables, styles refined,
The code grows clearer, all neatly aligned.
With every commit, this garden does grow—
🐇 Cheers to the changes, onward we go!

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

yarn install v1.22.22
[1/4] Resolving packages...
(node:6994) [DEP0169] DeprecationWarning: url.parse() behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for url.parse() vulnerabilities.
(Use node --trace-deprecation ... to show where the warning was created)
[2/4] Fetching packages...
error nx@21.0.3: The engine "node" is incompatible with this module. Expected version "^20.19.0 || ^22.12.0". Got "24.2.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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 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
vercel bot commented Jun 25, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
cosmos ❌ Failed (Inspect) Jun 25, 2025 11:04am
cowfi ✅ Ready (Inspect) Visit Preview Jun 25, 2025 11:04am
explorer-dev ✅ Ready (Inspect) Visit Preview Jun 25, 2025 11:04am
sdk-tools ✅ Ready (Inspect) Visit Preview Jun 25, 2025 11:04am
swap-dev ✅ Ready (Inspect) Visit Preview Jun 25, 2025 11:04am
widget-configurator ✅ Ready (Inspect) Visit Preview Jun 25, 2025 11:04am

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

🧹 Nitpick comments (2)
apps/cowswap-frontend/src/modules/orderProgressBar/pure/steps/BridgingStep.tsx (1)

34-36: Add a fallback colour for robustness.
If UI.COLOR_PAPER_DARKER is not injected into the runtime CSS variables, the element will render with unset background. Consider supplying a fallback.

-  background: var(${UI.COLOR_PAPER_DARKER});
+  /* Fallback keeps legacy colour when CSS variable is absent */
+  background: var(${UI.COLOR_PAPER_DARKER}, #f2f2f2);
apps/cowswap-frontend/src/modules/bridge/pure/CollapsibleBridgeRoute/index.tsx (1)

38-40: Remove obsolete TODO comment.

The TODO is now satisfied; keep the file tidy.

-  // TODO: Add proper return type annotation
   const toggleExpanded = (): void => setIsExpanded((state) => !state)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bf1fada and ece4f4d.

📒 Files selected for processing (4)
  • apps/cowswap-frontend/src/cosmos.decorator.tsx (2 hunks)
  • apps/cowswap-frontend/src/modules/bridge/pure/CollapsibleBridgeRoute/index.tsx (1 hunks)
  • apps/cowswap-frontend/src/modules/bridge/pure/ProgressDetails/index.tsx (2 hunks)
  • apps/cowswap-frontend/src/modules/orderProgressBar/pure/steps/BridgingStep.tsx (2 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
apps/cowswap-frontend/src/cosmos.decorator.tsx (1)
apps/cowswap-frontend/src/theme/ThemeConfigUpdater.ts (1)
  • ThemeConfigUpdater (13-30)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Setup
  • GitHub Check: Cypress
🔇 Additional comments (5)
apps/cowswap-frontend/src/cosmos.decorator.tsx (2)

24-24: Import path looks good.
The relative path resolves correctly (src/theme/ThemeConfigUpdater). No concerns.


110-112: Verify side-effect duplication under React StrictMode.
ThemeConfigUpdater fires a useEffect that writes to the Jotai atom every time it mounts. Because StrictMode intentionally mounts components twice in development, the atom will be set twice. That is generally harmless but can spam dev tools/loggers if future logic adds expensive work inside the same effect.

apps/cowswap-frontend/src/modules/orderProgressBar/pure/steps/BridgingStep.tsx (1)

3-3: Named import verified.
UI is now required for theme tokens; the bundle size impact is negligible.

apps/cowswap-frontend/src/modules/bridge/pure/ProgressDetails/index.tsx (1)

1-2: Explicit return type improves readability.
Nice cleanup and ESLint-compliance.

apps/cowswap-frontend/src/modules/bridge/pure/CollapsibleBridgeRoute/index.tsx (1)

33-34: Return type annotation added.
This removes the need for the previous ESLint suppression – good improvement.

@elena-zh
Copy link
Contributor

This issue has been addressed in #5782

@shoom3301 shoom3301 merged commit 13bd0a9 into develop Jun 25, 2025
13 of 15 checks passed
@shoom3301 shoom3301 deleted the fix/progress-theme-bg branch June 25, 2025 14:07
@github-actions github-actions bot locked and limited conversation to collaborators Jun 25, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0