Skip to content

chore(ask_sb): Allow for multiple user feedback#395

Merged
brendan-kellam merged 3 commits intomainfrom
bkellam/chat_multi_feedback
Jul 25, 2025
Merged

chore(ask_sb): Allow for multiple user feedback#395
brendan-kellam merged 3 commits intomainfrom
bkellam/chat_multi_feedback

Conversation

@brendan-kellam
Copy link
Copy Markdown
Contributor

@brendan-kellam brendan-kellam commented Jul 25, 2025

This PR changes the feedback behaviour to allow multiple items of feedback for a given message.

Summary by CodeRabbit

  • New Features

    • Enhanced feedback functionality to support multiple feedback entries per message, allowing users to submit feedback more than once.
  • Refactor

    • Updated feedback handling in chat messages to improve consistency and future extensibility.
    • Feedback state in answer cards is now managed internally, streamlining the user interface.

@brendan-kellam brendan-kellam requested a review from msukkari July 25, 2025 16:51
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 25, 2025

"""

Walkthrough

The changes update how user feedback on chat messages is stored and managed. Feedback is now kept as an array of entries in message metadata, supporting multiple feedback actions. The related prop and state logic in the AnswerCard component were simplified to remove external feedback state, and types were updated to reflect the new feedback structure.

Changes

File(s) Change Summary
packages/web/src/features/chat/actions.ts Modified submitFeedback to append feedback as array entries in message metadata; type assertion added.
packages/web/src/features/chat/components/chatThread/answerCard.tsx Removed feedback prop from AnswerCardProps and component; feedback state now only internal.
packages/web/src/features/chat/components/chatThread/chatThreadListItem.tsx Stopped passing feedback prop to AnswerCard from message metadata.
packages/web/src/features/chat/types.ts Changed feedback in schema from optional object to optional array of feedback objects.
CHANGELOG.md Reordered "Fixed" section below "Added" under "Unreleased" without content changes.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant AnswerCard
    participant ChatThreadListItem
    participant Actions (submitFeedback)
    participant MessageMetadata

    User->>AnswerCard: Clicks Like/Dislike
    AnswerCard->>Actions (submitFeedback): Calls submitFeedback(type)
    Actions (submitFeedback)->>MessageMetadata: Appends feedback entry to feedback array
    MessageMetadata-->>Actions (submitFeedback): Updated metadata
    Actions (submitFeedback)-->>AnswerCard: (Optional) Confirmation/Update
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

In the chat where feedback flows,
Now an array, not just one rose!
Cards keep secrets, state inside,
No more props from outside ride.
Types align, the schema grows—
A garden of feedback, in tidy rows.
🐇✨
"""

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 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 1c8b29e and beb502c.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • CHANGELOG.md
⏰ 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: build
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch bkellam/chat_multi_feedback

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 generate unit tests to generate unit tests for 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.

@github-actions

This comment has been minimized.

Copy link
Copy Markdown
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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 74e37d1 and 1c8b29e.

📒 Files selected for processing (4)
  • packages/web/src/features/chat/actions.ts (2 hunks)
  • packages/web/src/features/chat/components/chatThread/answerCard.tsx (1 hunks)
  • packages/web/src/features/chat/components/chatThread/chatThreadListItem.tsx (0 hunks)
  • packages/web/src/features/chat/types.ts (1 hunks)
💤 Files with no reviewable changes (1)
  • packages/web/src/features/chat/components/chatThread/chatThreadListItem.tsx
🧰 Additional context used
📓 Path-based instructions (1)
**/*

📄 CodeRabbit Inference Engine (.cursor/rules/style.mdc)

Filenames should always be camelCase. Exception: if there are filenames in the same directory with a format other than camelCase, use that format to keep things consistent.

Files:

  • packages/web/src/features/chat/types.ts
  • packages/web/src/features/chat/actions.ts
  • packages/web/src/features/chat/components/chatThread/answerCard.tsx
⏰ 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: build
🔇 Additional comments (2)
packages/web/src/features/chat/types.ts (1)

48-52: LGTM! Schema correctly updated to support multiple feedback entries.

The change from a single feedback object to an array of feedback objects properly enables storing multiple feedback entries per message, which aligns with the PR objectives.

packages/web/src/features/chat/actions.ts (1)

249-258: LGTM! Feedback appending logic correctly implemented.

The function now properly appends new feedback entries to the existing array while preserving previous feedback. The spread operator with nullish coalescing (?? []) correctly handles the case where no previous feedback exists, and the type assertion ensures type safety.

Comment thread packages/web/src/features/chat/components/chatThread/answerCard.tsx
msukkari
msukkari previously approved these changes Jul 25, 2025
@brendan-kellam brendan-kellam merged commit efc9656 into main Jul 25, 2025
6 checks passed
@brendan-kellam brendan-kellam deleted the bkellam/chat_multi_feedback branch July 25, 2025 20:21
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.

2 participants