Skip to content

Conversation

AshishViradiya153
Copy link
Contributor

@AshishViradiya153 AshishViradiya153 commented Sep 16, 2025

Summary by CodeRabbit

  • Style
    • Updated helper text styling under “Question” fields in FAQ modals for clearer, theme-consistent appearance.
    • Adjusted new message input and “New Question” textarea to use background and foreground theme colors for better readability in different themes.
    • Refined FAQ section colors: “Q” label now uses standard foreground color; answer text uses muted foreground for improved contrast hierarchy.
    • Overall visual consistency improved across conversation viewer and FAQ flows without changing functionality or behavior.

Copy link

vercel bot commented Sep 16, 2025

@AshishViradiya153 is attempting to deploy a commit to the mftsio Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Sep 16, 2025

Walkthrough

UI-only className updates across FAQ modals, conversation sidebar inputs, and FAQ section labels. Colors and tokens switched to design-system variables (e.g., text-muted-foreground, text-foreground, bg-background). No logic, state, data flow, or exports changed.

Changes

Cohort / File(s) Summary of Changes
Dashboard FAQ modals
ee/features/conversations/components/dashboard/edit-faq-modal.tsx, ee/features/conversations/components/dashboard/publish-faq-modal.tsx
Helper text under “Question” input: class changed from text-sm text-gray-500 to text-sm text-muted-foreground.
Viewer Conversation Sidebar
ee/features/conversations/components/viewer/conversation-view-sidebar.tsx
Added bg-background to new-message input and text-foreground to “New Question” textarea className.
Viewer FAQ section
ee/features/conversations/components/viewer/faq-section.tsx
Updated color tokens: Q label text-gray-900text-foreground; A content text-gray-700text-muted-foreground.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title "correct dark mode color styling" accurately and concisely reflects the primary change in the diff—updating CSS class tokens to improve dark-mode colors across multiple conversation/FAQ components—so it is relevant and focused for a reviewer scanning PRs. It is short, specific to the main purpose, and avoids noisy file lists or unrelated details.
✨ Finishing touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

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 (7)
ee/features/conversations/components/dashboard/edit-faq-modal.tsx (2)

173-176: Sweep remaining gray- text utilities to tokens for dark mode*

Several labels/descriptions still use text-gray-700/500. Prefer text-foreground or text-muted-foreground for theme consistency.

Apply this minimal patch:

-                <label className="text-sm font-medium text-gray-700">
+                <label className="text-sm font-medium text-foreground">
...
-                  <p className="mt-1 text-xs text-gray-500">
+                  <p className="mt-1 text-xs text-muted-foreground">
...
-                <label className="text-sm font-medium text-gray-700">
+                <label className="text-sm font-medium text-foreground">
...
-                  <p className="mt-1 text-xs text-gray-500">
+                  <p className="mt-1 text-xs text-muted-foreground">
...
-                            <div className="text-xs text-gray-500">
+                            <div className="text-xs text-muted-foreground">

Also applies to: 185-188, 192-195, 203-206, 267-269


176-188: Optional: replace blue/green panels with theme tokens or add dark variants

The “Original Question/Answer” panels use bg-blue-50/50, border-blue-200, bg-green-50/50, border-green-200. These wash out in dark mode. Options:

  • Neutral tokens: bg-muted border, keep icon color accents.
  • Or add dark: overrides (e.g., dark:bg-blue-950/40 dark:border-blue-400/30 and equivalents for green).

Your call based on design intent.

Also applies to: 195-207

ee/features/conversations/components/dashboard/publish-faq-modal.tsx (3)

243-246: Unify remaining gray- text classes to tokens*

Same sweep here for consistency with the PR goal.

-                <label className="text-sm font-medium text-gray-700">
+                <label className="text-sm font-medium text-foreground">
...
-                  <p className="mt-1 text-xs text-gray-500">
+                  <p className="mt-1 text-xs text-muted-foreground">
...
-                <label className="text-sm font-medium text-gray-700">
+                <label className="text-sm font-medium text-foreground">
...
-                  <p className="mt-1 text-xs text-gray-500">
+                  <p className="mt-1 text-xs text-muted-foreground">
...
-                            <div className="text-xs text-gray-500">
+                            <div className="text-xs text-muted-foreground">

Also applies to: 253-260, 264-267, 274-281, 343-345


246-261: Optional: accent panels in fixed blue/green scales

Consider bg-muted/border tokens, or add dark: equivalents to current blue/green backgrounds/borders to avoid low contrast in dark mode.

Also applies to: 267-281


1-376: Convert remaining hard-coded Tailwind color classes to design tokens

Occurrences found — replace these Tailwind color utility classes with the appropriate design tokens/component token classes:

  • ee/features/conversations/components/viewer/faq-section.tsx
    • line 123: className="bg-gray-50 p-4 dark:bg-gray-900"
    • line 135: className="rounded-md border border-gray-200 bg-white"
    • line 155: className="bg-gray-50 p-4 dark:bg-gray-900"
    • line 176: className="flex-shrink-0 bg-gray-50 dark:bg-gray-900"
    • line 204: className="rounded-md border border-gray-200 bg-white"
  • ee/features/conversations/components/dashboard/publish-faq-modal.tsx
    • line 243: className="text-sm font-medium text-gray-700"
    • line 246: className="mt-2 rounded-lg border border-blue-200 bg-blue-50/50 p-3"
    • line 253: className="mt-1 text-xs text-gray-500"
    • line 264: className="text-sm font-medium text-gray-700"
    • line 267: className="mt-2 rounded-lg border border-green-200 bg-green-50/50 p-3"
    • line 274: className="mt-1 text-xs text-gray-500"
    • line 343: className="text-xs text-gray-500"
  • ee/features/conversations/components/dashboard/edit-faq-modal.tsx
    • line 173: className="text-sm font-medium text-gray-700"
    • line 176: className="mt-2 rounded-lg border border-blue-200 bg-blue-50/50 p-3"
    • line 185: className="mt-1 text-xs text-gray-500"
    • line 192: className="text-sm font-medium text-gray-700"
    • line 195: className="mt-2 rounded-lg border border-green-200 bg-green-50/50 p-3"
    • line 203: className="mt-1 text-xs text-gray-500"
    • line 267: className="text-xs text-gray-500"
  • ee/features/conversations/components/dashboard/conversations-not-enabled-banner.tsx
    • line 132: className="mb-6 border-gray-200 bg-gray-50 dark:border-gray-700 dark:bg-gray-800"
    • line 167: className="mb-6 border-gray-200 bg-gray-50 dark:border-gray-700 dark:bg-gray-800"
    • line 264: className="rounded-b-lg border-t bg-gray-200 px-6 py-4 dark:bg-gray-700"
ee/features/conversations/components/viewer/conversation-view-sidebar.tsx (1)

300-305: Nit: verify icon color in default vs ghost states

BellIcon uses text-background for the “enabled/default” button. Ensure sufficient contrast across themes; text-primary-foreground may be safer inside a default button.

-  {activeConversation.receiveNotifications ? (
-    <BellIcon className="h-5 w-5 text-background" />
+  {activeConversation.receiveNotifications ? (
+    <BellIcon className="h-5 w-5 text-primary-foreground" />
   ) : (
     <BellOffIcon className="h-5 w-5 text-muted-foreground" />
   )}
ee/features/conversations/components/viewer/faq-section.tsx (1)

120-171: Broaden tokenization: container, cards, and scroll blur

  • Containers/cards still use bg-gray-50/dark:bg-gray-900, bg-white, border-gray-200. Prefer tokens for theme parity.

Examples:

-        <div className="bg-gray-50 p-4 dark:bg-gray-900">
+        <div className="bg-muted p-4">
...
-                    className="rounded-md border border-gray-200 bg-white"
+                    className="rounded-md border bg-card text-card-foreground"
  • Scroll gradients use gray scales. Consider background tokens:
- from-gray-50 via-gray-50/80 ... dark:from-gray-900 dark:via-gray-900/80
+ from-background via-background/80 ...  /* (same for dark via CSS vars) */

Also applies to: 204-206, 236-241

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4a0d3aa and 21c5da5.

📒 Files selected for processing (4)
  • ee/features/conversations/components/dashboard/edit-faq-modal.tsx (1 hunks)
  • ee/features/conversations/components/dashboard/publish-faq-modal.tsx (1 hunks)
  • ee/features/conversations/components/viewer/conversation-view-sidebar.tsx (2 hunks)
  • ee/features/conversations/components/viewer/faq-section.tsx (2 hunks)
🔇 Additional comments (4)
ee/features/conversations/components/dashboard/edit-faq-modal.tsx (1)

223-225: LGTM: token swap to text-muted-foreground

This aligns with the design tokens and fixes dark‑mode contrast for the helper text.

ee/features/conversations/components/dashboard/publish-faq-modal.tsx (1)

298-301: LGTM: helper text moved to text-muted-foreground

Matches design tokens and improves dark‑mode readability.

ee/features/conversations/components/viewer/conversation-view-sidebar.tsx (1)

345-347: LGTM: bg-background/text-foreground on inputs/textarea

Good dark‑mode defaults with placeholder:text-muted-foreground and ring tokens.

Also applies to: 386-388

ee/features/conversations/components/viewer/faq-section.tsx (1)

211-213: LGTM: tokenized Q/A text colors

  • Q label text → text-foreground
  • A text → text-muted-foreground

Both are theme-safe.

Also applies to: 223-225

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