Skip to content

docs: rename data to JSON and dataframe to table#12352

Open
mendonk wants to merge 5 commits intorelease-1.9.0from
docs-rename-data-to-json
Open

docs: rename data to JSON and dataframe to table#12352
mendonk wants to merge 5 commits intorelease-1.9.0from
docs-rename-data-to-json

Conversation

@mendonk
Copy link
Copy Markdown
Collaborator

@mendonk mendonk commented Mar 26, 2026

#11554
Mostly find and replace except for:
Release notes
Data types

@mendonk mendonk requested a review from aimurphy March 26, 2026 19:33
@mendonk mendonk self-assigned this Mar 26, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 26, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f8bc7d13-45a7-404a-877d-421678d08da2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs-rename-data-to-json

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Mar 26, 2026
@github-actions

This comment has been minimized.

@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Mar 26, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 26, 2026

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Mar 26, 2026
Copy link
Copy Markdown
Member

@Cristhianzl Cristhianzl left a comment

Choose a reason for hiding this comment

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

lgtm

@github-actions github-actions bot added the lgtm This PR has been approved by a maintainer label Mar 26, 2026
Copy link
Copy Markdown
Collaborator

@aimurphy aimurphy left a comment

Choose a reason for hiding this comment

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

approved with some suggestions/questions

| Name | Type | Description |
|------|------|-------------|
| data_inputs | Data/DataFrame | The data with documents to split in chunks. |
| data_inputs | JSON/Table | The data with documents to split in chunks. |
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Optional, out of scope

Suggested change
| data_inputs | JSON/Table | The data with documents to split in chunks. |
| data_inputs | JSON or Table | The data with documents to split in chunks. |

| Name | Type | Description |
|------|------|-------------|
| data_inputs | Data/DataFrame | The data with documents to export. |
| data_inputs | JSON/Table | The data with documents to export. |
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
| data_inputs | JSON/Table | The data with documents to export. |
| data_inputs | JSON or Table | The data with documents to export. |

| Name | Display Name | Info |
|------|--------------|------|
| data | Data | Input parameter. The `Data` object to operate on. |
| data | JSON | Input parameter. The `JSON` object to operate on. |
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

To avoid confusion with any regular JSON object, it might be worth reiterating here that this must be the JSON data type (i.e. it cannot be JSON within a table or message).

Suggested change
| data | JSON | Input parameter. The `JSON` object to operate on. |
| data | JSON | Input parameter. The `JSON` object to operate on. Must be provided as `JSON` data type input generated by another component. If the preceding component doesn't produce `JSON` output, use the [**Type Convert** component](/type-convert) to reformat the data before passing it to the **JSON Operations** component. |

Use the **JQ Expressions** operation to use the [jq](https://jqlang.org/) query language to perform more advanced JSON filtering.
1. In the **Operations** dropdown, select **JQ Expression**.
2. In the **JQ Expression** field, enter a `jq` filter to query against the **Data Operations** component's Data input.
2. In the **JQ Expression** field, enter a `jq` filter to query against the **JSON Operations** component's JSON input.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
2. In the **JQ Expression** field, enter a `jq` filter to query against the **JSON Operations** component's JSON input.
2. In the **JQ Expression** field, enter a `jq` filter to query against the **JSON Operations** component's **JSON** input.

The **DataFrame Operations** component performs operations on [`DataFrame`](/data-types#dataframe) (table) rows and columns, including schema changes, record changes, sorting, and filtering.
For all options, see [DataFrame Operations parameters](#dataframe-operations-parameters).
:::tip
Prior to Langflow 1.9.0, this component was named **Data Operations**.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Prior to Langflow 1.9.0, this component was named **Data Operations**.
Prior to Langflow 1.9.0, this component was named **DataFrame Operations**.


**Data** ports <Icon name="Circle" size="16" aria-label="Red data port" style={{ color: '#dc2626', fill: '#dc2626' }} /> accept or produce the `Data` type, which is a structured data object, like a JSON payload that you might send to an API.
:::tip
Prior to version 1.9.0, the JSON port was called `Data`.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Optional

Suggested change
Prior to version 1.9.0, the JSON port was called `Data`.
In Langflow version 1.9.0, the `Data` type and port were renamed to `JSON`.

- `default_value`: Fallback if `text_key` is missing. The default `text_key` is `"text"`.

```python
data_obj = Data(
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

JSON or Json?

Suggested change
data_obj = JSON(

## Table

:::tip
Prior to version 1.9.0, the Table port was called `DataFrame`.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Prior to version 1.9.0, the Table port was called `DataFrame`.
In Langflow version 1.9.0, the `DataFrame` type and port were renamed to `Table`.

- Renamed `Data` and `DataFrame` types

The `Data` object is now named `JSON`, and the `DataFrame` object is now named `Table`.
The **Data Operations** component is now the [**JSON Operations** component](/data-operations), and the **DataFrame Operations** component is now the [**Table Operations** component](/dataframe-operations).
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I think I would separate the sentence about the component names into it's own bullet - Renamed the **Data Operations** and **DataFrame Operations** components

Comment on lines +286 to +295
{
type: "doc",
id: "Components/data-operations",
label: "JSON Operations",
},
{
type: "doc",
id: "Components/dataframe-operations",
label: "Table Operations",
},
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

The page title is the same a the label so you can still use the shorthand.

Suggested change
{
type: "doc",
id: "Components/data-operations",
label: "JSON Operations",
},
{
type: "doc",
id: "Components/dataframe-operations",
label: "Table Operations",
},
"Components/data-operations",
"Components/dataframe-operations",

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants