fix: toastify fix

[kemuru]

PR-Codex overview

This PR focuses on updating the global styles in the global-style.ts file, specifically adjusting the styling for toast notifications.

Detailed summary

• Removed the --os-handle-bg-active variable.
• Added a new CSS rule for elements with a class containing Toastify__toast-container:
  • Set top to unset.
  • Set padding-top to 20px with !important priority.

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

Summary by CodeRabbit

• Style
  • Enhanced the visual layout of notifications by adjusting the top spacing and adding extra padding for better alignment. This update ensures that notifications are properly spaced and visually distinct, enhancing the overall user experience without altering existing styles.

[coderabbitai]

Walkthrough

A new CSS rule has been added to the global styles. The rule targets elements with class names containing "Toastify__toast-container" and sets top to unset with a padding-top of 20px !important. There are no removals or modifications of existing styles.

Changes

File	Change Summary
web/.../global-style.ts	Added a new CSS rule for elements with class names including "Toastify__toast-container" to set top: unset and padding-top: 20px !important.

Poem

I'm a bunny with a fresh new tweak,
Hopping through styles, so sleek and unique.
CSS carrots and toast delight,
Making every container just feel right.
A hop of joy in every line,
Hop on board, the style's divine!

---

📜 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 a596f10 and b8d1f52.

📒 Files selected for processing (1)

• web/src/styles/global-style.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Redirect rules - curate-v2
• GitHub Check: Header rules - curate-v2
• GitHub Check: Pages changed - curate-v2

🔇 Additional comments (1)

web/src/styles/global-style.ts (1)

120-123:

✅ Verification successful

LGTM! Consider adding a comment to explain the override.

The CSS rule effectively fixes the toast positioning. While the use of !important is generally discouraged, it's often necessary when overriding third-party component styles.

Consider adding a comment to explain why the !important flag is necessary:

  [class*="Toastify__toast-container"] {
+   /* Override react-toastify's default positioning to prevent overlap with header */
    top: unset;
    padding-top: 20px !important;
  }

---

🌐 Web query:

What is the default positioning of react-toastify containers and why might we need to override it?

💡 Result:

By default, React-Toastify positions notification containers at the top-right of the browser viewport[1][4][5][7][9]. This standard placement works for most applications but might require customization in specific scenarios.

Key reasons to override default positioning:

1. Design system alignment
   Applications with left-aligned navigation or right-side interactive elements often conflict with top-right notifications[8]. Repositioning prevents visual clashes with critical UI components.

2. Contextual notification hierarchy
   Different message types benefit from strategic placement:

   • Critical errors: Bottom-center for maximum visibility[7]
   • Success confirmations: Top-center as transient acknowledgments[5]
   • Background processes: Bottom-right to avoid workflow interruption[9]

3. Viewport optimization
   Mobile-first designs frequently use bottom positioning (bottom-center/bottom-right) to prevent keyboard overlap during form input[10].

4. Multi-container configurations
   Complex applications may require separate containers for different notification categories:

   // Main app container
   <ToastContainer position="top-center" />
   
   // Chat widget container
   <ToastContainer 
     position="bottom-left"
     className="chat-notifications"
   />

5. Accessibility requirements
   Screen reader users might need notifications positioned in specific screen regions based on WCAG guidelines[5][7].

To customize positioning, developers can either:

• Set global positioning via ToastContainer:

  <ToastContainer position="bottom-left" />

• Override per notification:

  toast.error('Payment failed', { 
    position: 'top-center' 
  });

The library provides six predefined positions through its POSITION enum[1][4], but advanced use cases can implement custom CSS positioning through class overrides[2][8].

Citations:

• 1: https://fkhadra.github.io/react-toastify/positioning-toast/
• 2: https://fkhadra.github.io/react-toastify/how-to-style/
• 3: Styling a position of the container with styled components fkhadra/react-toastify#639
• 4: https://material-react-toastify.netlify.app/positioning-toast/
• 5: https://www.fynd.academy/blog/react-toastify
• 6: https://fkhadra.github.io/react-toastify/introduction/
• 7: https://blog.openreplay.com/style-your-toast-messages-with-react-toastify/
• 8: Custom container position fkhadra/react-toastify#263
• 9: https://blog.logrocket.com/using-react-toastify-style-toast-messages/
• 10: Is there a way to give the toast a custom position above/left/right or below relative to another React component/DOM element? fkhadra/react-toastify#391

---

Action Required: Document the Reason for Overriding React-Toastify's Default Positioning

The new CSS rule correctly resets the toast container’s positioning by unsetting the default top value and enforcing a 20px top padding. As React-Toastify normally positions its containers in the top-right corner, this override is likely implemented to avoid layout conflicts—such as overlapping with headers or other UI elements—especially in custom design systems.

While the use of !important is acceptable here to ensure precedence over third-party styles, please add an inline comment to clarify the rationale for future maintainers.

For example:

  [class*="Toastify__toast-container"] {
+   /* Override react-toastify's default top-right positioning to prevent overlap with the header */
    top: unset;
    padding-top: 20px !important;
  }

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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

[netlify]

✅ Deploy Preview for curate-v2 ready!

Name	Link
🔨 Latest commit	b8d1f52
🔍 Latest deploy log	https://app.netlify.com/sites/curate-v2/deploys/67b3b856ed0b1c0008bb2b89
😎 Deploy Preview	https://deploy-preview-73--curate-v2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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