-
Notifications
You must be signed in to change notification settings - Fork 0
PRD-2076: Fix isResponseGenerating behavior #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
PRD-2076: Fix isResponseGenerating behavior #9
Conversation
|
@veliseev93 please take a look |
|
@Tomass673 I see the patch applied to the |
I left them there as is, because commit from child branch will overwrite this changes |
|
|
||
| const history = chat?.chat.history; | ||
| const isResponseGenerating = !history?.messages[history.currentId].done; | ||
| const isResponseGenerating = history?.lastAssistantMessage?.done !== true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes related to lastAssistantMessage cause a bug when switching message history. If we return to an old chat thread, the input becomes disabled.
| if (!modelId) return; | ||
|
|
||
| // mark message as not completed | ||
| patchChatQueryData(chatId, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this change is enough to fix the original bug, why do we need the rest of the changes?
Task: https://app.clickup.com/t/24336023/PRD-2076?comment=90150176676710