langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #12352] fix: fix issue with chat-input-area clearing during Responding state. #27616

New Issue
Closed
opened 2026-02-21 20:41:52 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:41:52 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/12352

State: closed
Merged: Yes

Summary

Resolves #11849

This PR is a resubmission as requested, as part of the now-closed #11850 .

Fixed

  • Fix the issue where the chat-input-area was cleared in response state
    • Fixed the issue where the input box content was cleared after sending a message in response state. Now, it will check if the state is in response mode, and if so, it will display a prompt and retain the input box content.

Modification Details

This section was automatically generated by GitHub Copilot actions.

This pull request includes changes to the ChatInputArea component to handle the scenario when a response is already being processed. The most important changes include adding a new isResponding property to the component's props and implementing a check to notify the user if a response is in progress.

Enhancements to ChatInputArea component:

Integration with Chat component:

Checklist

Important

Please review the checklist below before submitting your pull request.

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/12352 **State:** closed **Merged:** Yes --- # Summary Resolves #11849 ***This PR is a resubmission as requested, as part of the now-closed #11850 .*** ## Fixed - Fix the issue where the `chat-input-area` was cleared in response state - Fixed the issue where the input box content was cleared after sending a message in response state. Now, it will check if the state is in response mode, and if so, it will display a prompt and retain the input box content. # Modification Details > This section was automatically generated by `GitHub Copilot actions`. This pull request includes changes to the `ChatInputArea` component to handle the scenario when a response is already being processed. The most important changes include adding a new `isResponding` property to the component's props and implementing a check to notify the user if a response is in progress. Enhancements to `ChatInputArea` component: * [`web/app/components/base/chat/chat/chat-input-area/index.tsx`](diffhunk://#diff-0f2fea1c6856ffaf8e9ad3be67d02e176e4ed92c585847813210b58a642c2767R42): Added `isResponding` property to `ChatInputAreaProps` and included it in the component's destructured props. [[1]](diffhunk://#diff-0f2fea1c6856ffaf8e9ad3be67d02e176e4ed92c585847813210b58a642c2767R42) [[2]](diffhunk://#diff-0f2fea1c6856ffaf8e9ad3be67d02e176e4ed92c585847813210b58a642c2767R55) * [`web/app/components/base/chat/chat/chat-input-area/index.tsx`](diffhunk://#diff-0f2fea1c6856ffaf8e9ad3be67d02e176e4ed92c585847813210b58a642c2767R82-R86): Implemented a check in the `handleSend` function to notify the user if a response is already being processed, preventing multiple simultaneous responses. Integration with `Chat` component: * [`web/app/components/base/chat/chat/index.tsx`](diffhunk://#diff-1997e9de3191a3a5147e5a628bb6b4bec22e6af48b4e3907a56d4a7fbcac73c4R295): Passed the `isResponding` prop to the `ChatInputArea` component to ensure the new functionality is integrated. # Checklist > [!IMPORTANT] > Please review the checklist below before submitting your pull request. - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:41:52 -05:00
yindo closed this issue 2026-02-21 20:41:52 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
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: langgenius/dify#27616
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?