Optimization of Chat component, other bug fixes. Resolves #11848 #11849 #11850
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
We have resolved the issues and improvements mentioned in issues #11848 and #11849.
Resolves #11848
Resolves #11849
New Features
Chat
componentChat
component could only display the most recent 40 messages, making it impossible to view earlier messages. This update introduces an upward scrolling feature that allows users to load more historical messages when they scroll to the top of the chat window.Fixes
Fix the issue where the opening statement generated by the
AutomaticRes
component were not synchronized between statesAutomaticRes
component would not automatically apply to the current orchestration state and needed to be saved to take effect. Now, the opening statement will automatically sync with the current orchestration state.Fix the style issue with the
WeightedScore
componentWeightedScore
component slightly overlapped with other elements.Fix the issue of Echarts charts and Markdown tables being too wide in conversations
Add missing i18n items
Fix the issue where the
chat-input-area
was cleared in response stateFix the issue where old replies were displayed after regenerating a reply and switching conversations
Fix the issue where
TextGeneration
component does not correctly clear input dataTextGeneration
component did not properly reset references when clearing the form. This issue caused old form values to be automatically filled in upon re-entering data. Now, the form references are correctly reset after clearing, ensuring that new input data is not affected by previous values.Tip
Close issue syntax:
Fixes #<issue number>
orResolves #<issue number>
, see documentation for more details.Screenshots
Checklist
Important
Please review the checklist below before submitting your pull request.
dev/reformat
(backend) andcd web && npx lint-staged
(frontend) to appease the lint gods