The keys of the nodeIcons object have been renamed to improve semantics and readability. The new names are more descriptive of the functionality of the corresponding icons.
The "suffix" and "prefix" fields have been changed from type "str" to "prompt" to allow for more flexibility in the input. The "format_instructions" field has been updated to be required and multiline, and to show the instructions by default. This change will make it easier for users to understand the expected input format.
🔨 refactor(util.py): add format_instructions to the list of fields to format in format_dict function
The suffix and format_instructions fields in the ZeroShotPromptNode class were swapped to improve the readability of the code. The format_instructions field is now above the suffix field, which makes more sense as it is a required field. In the util.py file, the format_instructions field was added to the list of fields to format in the format_dict function. This ensures that the format_instructions field is properly formatted when the function is called.
Description:
This pull request proposes the addition of a scrollbar to the modal
window containing advanced settings when the number of input fields
exceeds the limit of the screen. This enhancement aims to improve user
experience by providing a convenient way to access all settings, even
when the available screen space is limited.
The number of inputs in the screen is limited by a variable on Utils
that can be easily changed in the future if It's needed.
✨ feat(template): add method to add fields to a template
The VectorStoreFrontendNode now supports adding extra fields to its
template. The add_extra_fields method is called after the node is loaded
and adds the weaviate_url field to the template if the node is of type
Weaviate. The Template class now has a method to add fields to a
template. This method is used by the VectorStoreFrontendNode to add the
weaviate_url field to its template.
✨ feat(template): add method to add fields to a template
The VectorStoreFrontendNode now supports adding extra fields to its template. The add_extra_fields method is called after the node is loaded and adds the weaviate_url field to the template if the node is of type Weaviate. The Template class now has a method to add fields to a template. This method is used by the VectorStoreFrontendNode to add the weaviate_url field to its template.
The changes in this commit are purely cosmetic, as the code has been formatted with prettier to improve its readability and consistency. No functional changes have been made.
The langchain and langchain-serve dependencies have been updated to versions 0.0.184 and 0.0.38 respectively. This update may include bug fixes, performance improvements, or new features.
Description:
This pull request implements several UI feature enhancements to improve
the user experience. The changes include title casing on names and
titles, fixing and changing icons, and adding a cursor pointer on the
chat interface.
Changes Made:
Title case on names and titles: Modified the code to convert names and
titles to title case. This ensures consistent capitalization and
enhances readability throughout the application.
Fixing/Changing icons: Replaced outdated or inconsistent icons with
updated versions to provide a more visually appealing and cohesive user
interface.
Cursor on chat: Added a cursor pointer to the chat interface to indicate
interactivity and enhance user engagement. The cursor appears when
hovering over the chat area, making it clear that the chat is responsive
to user input.
Added new text splitters to the configuration file: RecursiveCharacterTextSplitter, LatexTextSplitter, and PythonCodeTextSplitter. These text splitters will be used to split text into smaller chunks for processing. Also, added new toolkits to the configuration file: OpenAPIToolkit and JsonToolkit. These toolkits will be used to process the text chunks generated by the text splitters.
This pull request resolves a bug related to error handling when
components attempt to call the same modals within different flows. The
issue occurs due to a lack of proper validation and error handling in
the existing codebase. This bugfix aims to provide a comprehensive
solution to mitigate the problem and ensure a smoother user experience.
