Skip to content

Conversation

@andreashimin
Copy link
Contributor

@andreashimin andreashimin commented Aug 20, 2025

Description

This PR addresses a text answer preview issue where the preview data section was not properly displayed when data was available. The fix ensures that the preview data section is always rendered, but the explanatory text is conditionally shown based on whether preview data exists.

Implementation

The implementation follows a conditional rendering approach where:

  • Always Render: The preview data container and PreviewData component are always rendered to maintain consistent layout
  • Conditional Display: The explanatory text is only shown when hasPreviewData is true
  • State Management: Introduced a hasPreviewData variable to avoid repeated property access and improve readability

Actual Changes

Text Answer Preview Enhancement

  • Fixed Preview Data Display: Modified TextBasedAnswer.tsx to always render the preview data section
  • Conditional UI Elements: Added conditional rendering for explanatory text based on data availability
  • Improved State Handling: Introduced hasPreviewData variable for cleaner conditional logic
  • Layout Consistency: Ensured the preview data section maintains consistent spacing and structure

Summary by CodeRabbit

  • Bug Fixes

    • Preview section now consistently displayed, reducing layout shifts when no data is available.
    • Explanatory text shows only when relevant preview data exists, preventing confusing messages.
  • Refactor

    • Streamlined conditional rendering by always mounting the preview container and component, improving UI stability and responsiveness.

@andreashimin andreashimin requested a review from fredalai August 20, 2025 10:15
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 20, 2025

Walkthrough

The preview rendering logic in TextBasedAnswer.tsx was adjusted. A hasPreviewData boolean is introduced. The preview container and PreviewData component are now always rendered, with the “context window” note shown only when hasPreviewData is true. No exported signatures or mutations were changed.

Changes

Cohort / File(s) Summary
Home prompt thread preview rendering
wren-ui/src/components/pages/home/promptThread/TextBasedAnswer.tsx
Introduced hasPreviewData flag; always renders outer preview container and PreviewData component; gates “context window” notice by hasPreviewData; no API/exports changed.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant U as User
  participant T as TextBasedAnswer
  participant D as previewDataResult
  participant P as PreviewData

  U->>T: Render component
  T->>D: Access data?.previewData
  D-->>T: previewData (maybe undefined)
  T->>T: hasPreviewData = Boolean(previewData)
  T->>P: Render PreviewData with previewData (possibly undefined)
  alt hasPreviewData
    T->>U: Show "context window limit" note
  else
    T->>U: Hide note
  end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I hop through code with whiskers keen,
A preview pane now always seen.
If data sprouts, a note will show—
If not, the winds of silence blow.
Two ears perked high, I merge with cheer,
Rendering clear, with burrows near. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/text-answer-preview

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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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
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 (3)
wren-ui/src/components/pages/home/promptThread/TextBasedAnswer.tsx (3)

119-119: Clarify “hasPreviewData” semantics (object vs. non-empty rows).

If “preview data exists” is meant to indicate non-empty rows, consider checking row count instead of truthiness of the container object.

-  const hasPreviewData = !!previewDataResult.data?.previewData;
+  const hasPreviewData =
+    (previewDataResult.data?.previewData?.data?.length ?? 0) > 0;

If the current behavior (showing the note when a previewData object exists, even with 0 rows) is intended, ignore this.


254-257: Avoid a brief “flash of empty” by treating the initial not-yet-called state as loading.

Before the mutation is called, loading is false and previewData is undefined, which can momentarily render an empty preview area. Consider leveraging Apollo’s called flag to keep the preview in a loading state until the first request is issued.

-              <PreviewData
-                error={previewDataResult.error}
-                loading={previewDataResult.loading}
-                previewData={previewDataResult?.data?.previewData}
-              />
+              <PreviewData
+                error={previewDataResult.error}
+                loading={previewDataResult.loading || !previewDataResult.called}
+                previewData={previewDataResult?.data?.previewData}
+              />

Please confirm that usePreviewDataMutation’s result exposes called in your codegen setup (it typically does for Apollo useMutation).


246-246: Minor a11y: Mark the preview region as busy while loading.

Helps assistive tech understand that content is being fetched/updated.

-            <div className="mt-2 mb-3" data-guideid="text-answer-preview-data">
+            <div
+              className="mt-2 mb-3"
+              data-guideid="text-answer-preview-data"
+              aria-busy={previewDataResult.loading}
+            >
📜 Review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between eabc6e4 and fe1aaed.

📒 Files selected for processing (1)
  • wren-ui/src/components/pages/home/promptThread/TextBasedAnswer.tsx (2 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
wren-ui/src/components/pages/home/promptThread/TextBasedAnswer.tsx (1)
wren-ui/src/components/dataPreview/PreviewData.tsx (1)
  • PreviewData (89-121)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Analyze (go)
🔇 Additional comments (1)
wren-ui/src/components/pages/home/promptThread/TextBasedAnswer.tsx (1)

246-258: LGTM: Always rendering the container and PreviewData fixes the visibility/layout regression.

This aligns with the PR objective: the preview area is now stable, and the explanatory text is shown only when data is present via hasPreviewData.

Copy link
Contributor

@fredalai fredalai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@andreashimin andreashimin merged commit 0c44ace into main Aug 21, 2025
7 checks passed
@andreashimin andreashimin deleted the fix/text-answer-preview branch August 21, 2025 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants