run-llama/create-llama
1
0
Fork 0
mirror of https://github.com/run-llama/create-llama.git synced 2026-07-16 11:04:26 -04:00
Code Issues 39 Packages Projects Releases 10 Wiki Activity

[PR #267] [MERGED] fix: dont use props as state in chat suggestion component #389

New Issue
Closed
opened 2026-02-15 19:17:30 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 19:17:30 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/create-llama/pull/267
Author: @thucpn
Created: 8/28/2024
Status: ✅ Merged
Merged: 8/29/2024
Merged by: @marcusschiesser

Base: main ← Head: fix/dont-use-props-as-state-in-chat-suggestion-component

📝 Commits (2)

  • 9b8fc19 fix: dont use props as state in chat suggestion component
  • 13f7ca3 Create old-readers-fix.md

📊 Changes

4 files changed (+15 additions, -4 deletions)

View changed files

➕ .changeset/old-readers-fix.md (+5 -0)
📝 templates/types/streaming/nextjs/app/components/ui/chat/chat-message/chat-suggestedQuestions.tsx (+3 -4)
📝 templates/types/streaming/nextjs/app/components/ui/chat/chat-message/index.tsx (+6 -0)
📝 templates/types/streaming/nextjs/app/components/ui/chat/chat-messages.tsx (+1 -0)

📄 Description

Summary by CodeRabbit

  • New Features

    • Enhanced chat suggestion component for improved data handling and performance.
    • Introduced a new isLastMessage prop across multiple components to enhance rendering logic based on message context.

  • Bug Fixes

    • Corrected the handling of properties in the chat suggestion component to prevent side effects and ensure consistent UI behavior.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/create-llama/pull/267 **Author:** [@thucpn](https://github.com/thucpn) **Created:** 8/28/2024 **Status:** ✅ Merged **Merged:** 8/29/2024 **Merged by:** [@marcusschiesser](https://github.com/marcusschiesser) **Base:** `main` ← **Head:** `fix/dont-use-props-as-state-in-chat-suggestion-component` --- ### 📝 Commits (2) - [`9b8fc19`](https://github.com/run-llama/create-llama/commit/9b8fc193410e204b662219ec7ca5b46c582300b3) fix: dont use props as state in chat suggestion component - [`13f7ca3`](https://github.com/run-llama/create-llama/commit/13f7ca34722b2611ea0414780fb9f5e4ab7621a1) Create old-readers-fix.md ### 📊 Changes **4 files changed** (+15 additions, -4 deletions) <details> <summary>View changed files</summary> ➕ `.changeset/old-readers-fix.md` (+5 -0) 📝 `templates/types/streaming/nextjs/app/components/ui/chat/chat-message/chat-suggestedQuestions.tsx` (+3 -4) 📝 `templates/types/streaming/nextjs/app/components/ui/chat/chat-message/index.tsx` (+6 -0) 📝 `templates/types/streaming/nextjs/app/components/ui/chat/chat-messages.tsx` (+1 -0) </details> ### 📄 Description <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced chat suggestion component for improved data handling and performance. - Introduced a new `isLastMessage` prop across multiple components to enhance rendering logic based on message context. - **Bug Fixes** - Corrected the handling of properties in the chat suggestion component to prevent side effects and ensure consistent UI behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 19:17:30 -05:00
yindo closed this issue 2026-02-15 19:17:30 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/create-llama#389
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?