Skip to content
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

docs: updates for release #6762

Open
wants to merge 21 commits into
base: main
Choose a base branch
from
Open

docs: updates for release #6762

wants to merge 21 commits into from

Conversation

mendonk
Copy link
Collaborator

@mendonk mendonk commented Feb 21, 2025

This pull request includes significant updates to the documentation for various components.

The most important changes include updates to the Structured Output component, the Chat Input and Chat Output components, and the Text Splitter component. Additionally, there is an update to the installation prerequisites for Langflow.

Documentation Updates:

  • docs/docs/Components/components-helpers.md: Enhanced the Structured Output component documentation by adding an example, updating the output_schema table, and providing more detailed descriptions of its parameters.

  • docs/docs/Components/components-io.md: Updated the Chat Input component to list the accepted input types and revised the input_value parameter description. Similar updates were made to the Chat Output component to list accepted input types. [1] [2]

  • docs/docs/Components/components-processing.md: Improved the Text Splitter component documentation by updating parameter descriptions, specifying default values, and adding a new text_key parameter.

Installation Prerequisites:

@mendonk mendonk added the DO NOT MERGE Don't Merge this PR label Feb 21, 2025
@mendonk mendonk self-assigned this Feb 21, 2025
@dosubot dosubot bot added size:L This PR changes 100-499 lines, ignoring generated files. documentation Improvements or additions to documentation labels Feb 21, 2025
@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Feb 21, 2025
@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Feb 21, 2025
@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Feb 21, 2025
@mendonk mendonk removed the DO NOT MERGE Don't Merge this PR label Feb 24, 2025
@github-actions github-actions bot removed the documentation Improvements or additions to documentation label Feb 24, 2025
@github-actions github-actions bot added the documentation Improvements or additions to documentation label Feb 24, 2025
Copy link
Collaborator

@edwinjosechittilappilly edwinjosechittilappilly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes suggested Above

@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Feb 25, 2025
@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Feb 25, 2025
@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Feb 25, 2025
@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Feb 25, 2025
@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Feb 25, 2025
Copy link
Collaborator

@edwinjosechittilappilly edwinjosechittilappilly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Feb 25, 2025
@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Feb 25, 2025
Copy link
Collaborator

@KimberlyFields KimberlyFields left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few comments, but approving.

* **Name**: The name of the output field.
* **Description**: The purpose of the output field.
* **Type**: The data type of the output field. The available types are `str`, `int`, `float`, `bool`, `list`, or `dict`. The default is `text`.
* **Multiple**: Deprecated feature, currently by default, it is set to `True` if you expect multiple values for a single field. For example, a `list` of `features` is set to `true` to contain multiple values, such as `["waterproof", "durable", "lightweight"]`. Default: `True`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* **Multiple**: Deprecated feature, currently by default, it is set to `True` if you expect multiple values for a single field. For example, a `list` of `features` is set to `true` to contain multiple values, such as `["waterproof", "durable", "lightweight"]`. Default: `True`.
* **Multiple**: This feature is deprecated. Currently, it is set to `True` by default if you expect multiple values for a single field. For example, a `list` of `features` is set to `True` to contain multiple values, such as `["waterproof", "durable", "lightweight"]`. Default: `True`.

* **Name**: The name of the output field.
* **Description**: The purpose of the output field.
* **Type**: The data type of the output field. The available types are `str`, `int`, `float`, `bool`, `list`, or `dict`. The default is `text`.
* **Multiple**: Deprecated feature, currently by default, it is set to `True` if you expect multiple values for a single field. For example, a `list` of `features` is set to `true` to contain multiple values, such as `["waterproof", "durable", "lightweight"]`. Default: `True`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a replacement for this deprecated option? What happens if a user used this option in the past?


The **Parse DataFrame** component parses the structured output into a template for orderly presentation in chat output. The template receives the values from the `output_schema` table with curly braces.

For example, the template `EBITIDA: {EBITIDA} , Net Income: {NET_INCOME} , GROSS_PROFIT: {GROSS_PROFIT}` presents the extracted values in the **Playground** as `EBITIDA: 900 million , Net Income: 500 million , GROSS_PROFIT: 1.2 billion`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be "EBITDA"?

| system_prompt | Format Instructions | Instructions to the language model for formatting the output. |
| schema_name | Schema Name | The name for the output data schema. |
| output_schema | Output Schema | Defines the structure and data types for the model's output.|
| multiple | Generate Multiple | [Deprecated] Always set to `True`. |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a replacement for the deprecated option? What happens if a user used this option in a previous release?

|should_store_message|Store Messages|Store the message in the history.|
|sender|Sender Type|The type of sender.|
|sender_name|Sender Name|The name of the sender.|
|session_id|Session ID|The session ID of the chat. If empty, the current session ID parameter will be used.|
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
|session_id|Session ID|The session ID of the chat. If empty, the current session ID parameter will be used.|
|session_id|Session ID|The session ID of the chat. If empty, the current session ID parameter is used.|

|should_store_message|Store Messages|The flag to store the message in the history.|
|sender|Sender Type|The type of sender.|
|sender_name|Sender Name|The name of the sender.|
|session_id|Session ID|The session ID of the chat. If empty, the current session ID parameter will be used.|
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
|session_id|Session ID|The session ID of the chat. If empty, the current session ID parameter will be used.|
|session_id|Session ID|The session ID of the chat. If empty, the current session ID parameter is used.|

|sender|Sender Type|The type of sender.|
|sender_name|Sender Name|The name of the sender.|
|session_id|Session ID|The session ID of the chat. If empty, the current session ID parameter will be used.|
|data_template|Data Template|The template to convert Data to Text. If left empty, it will be dynamically set to the Data's text key.|
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
|data_template|Data Template|The template to convert Data to Text. If left empty, it will be dynamically set to the Data's text key.|
|data_template|Data Template|The template to convert Data to Text. If the option is left empty, it is dynamically set to the Data's text key.|


### Outputs

| Name | Display Name | Info |
|------|--------------|------|
| data | Data | List of search results as Data objects |
| data | Data | List of search results as Data objects containing snippets and full content. |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is data capitalized in the Info column?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation lgtm This PR has been approved by a maintainer size:L This PR changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants