Skip to content

Conversation

@devinvillarosa
Copy link
Contributor

@devinvillarosa devinvillarosa commented Feb 18, 2025

Starts flow runs data table with basic columns. Will incrementally add columns based on original vue component .

Will also incrementally add server-side filters

Screenshot 2025-02-18 at 10 00 07 AM

Checklist

  • This pull request references any related issue by including "closes <link to issue>"
    • If no issue exists and your change is not a small fix, please create an issue first.
  • If this pull request adds new functionality, it includes unit tests that cover the changes
  • If this pull request removes docs files, it includes redirect settings in mint.json.
  • If this pull request adds functions or classes, it includes helpful docstrings.

Relates to #15512

@github-actions github-actions bot added the ui-replatform Related to the React UI rewrite label Feb 18, 2025
@devinvillarosa devinvillarosa marked this pull request as ready for review February 18, 2025 18:04
Comment on lines +12 to +14
export type FlowRunWithFlow = FlowRun & {
flow: Flow;
};
Copy link
Contributor

Choose a reason for hiding this comment

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

For context I believe this type is around mostly because the FlowRun model doesn't have flow_name but just flow_id. In cloud we recently added flow_name to the model and got rid of this type and the extra fetching to get the flow.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do you know if flow_name will be available for OSS soon?
I think this would help a lot in future development

Copy link
Contributor

Choose a reason for hiding this comment

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

idk that there's plan to do so but I'm sure we can make a plan to add it

Comment on lines +12 to +14
const meta: Meta<typeof FlowRunsDataTable> = {
title: "Components/FlowRuns/DataTable/FlowRunsDataTable",
decorators: [routerDecorator],
Copy link
Contributor

Choose a reason for hiding this comment

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

Ooo is this the fix for the router issues you mentioned last week?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is something else.
It just allows us to use router dependent components in stories without breaking,

The one I was mentioning last week is for tests

id: "deployment",
header: "Deployment",
cell: (props) => {
const deployment = props.getValue() as Deployment;
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it possible to make this type safe rather than using as? Maybe a type guard?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

edit: I think I've figured it out. Needed to define the table schema to be more specific to the table

};

type FlowRunsDataTableProps = {
flowRuns: Array<FlowRunWithDeploymentAndFlow | FlowRunWithFlow>;
Copy link
Contributor

Choose a reason for hiding this comment

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

FWIW I think the "WithDeployment..." type is around for the same reason as the WithFlow type. Because deployment_name doesn't exist on the flow run model. Just context, not requesting any change.

@devinvillarosa devinvillarosa force-pushed the start-flow-runs-data-table branch from 0ebd483 to 308ca66 Compare February 18, 2025 20:27
@devinvillarosa devinvillarosa merged commit 701e7f4 into main Feb 18, 2025
9 checks passed
@devinvillarosa devinvillarosa deleted the start-flow-runs-data-table branch February 18, 2025 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ui-replatform Related to the React UI rewrite

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants