[UI Feature] Ability to expand/collapse nodes on Execution Details

[ursucarina]

Motivation: Why do you think this is important?

To help user experience when dealing with deeply nested workflows

Goal: What should the final outcome look like, ideally?

+/- (expand/collapse) functionality on nodes tables

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes

[dosubot[bot]]

🤖

Hey @ursucarina! Great to see you bringing more ideas to the table. 👾

Thank you for your feature request. The ability to expand and collapse nodes in the Execution Details view would indeed be a valuable addition to the Flyte UI, especially for users dealing with deeply nested workflows.

Currently, the structure of the nodes table in the Execution Details view includes various fields such as NodeExecutionKey, Phase, InputURI, Closure, StartedAt, NodeExecutionCreatedAt, NodeExecutionUpdatedAt, Duration, NodeExecutionMetadata, ParentID, ChildNodeExecutions, ParentTaskExecutionID, LaunchedExecution, ErrorKind, ErrorCode, CacheStatus, DynamicWorkflowRemoteClosureReference, and InternalData. This structure is defined in the NodeExecution struct in the file flyteadmin/pkg/repositories/models/node_execution.go.

However, based on the information available in the repository, it's unclear whether the current version of Flyte's UI supports any form of node interaction in the Execution Details view, or how deeply nested workflows are currently displayed.

To implement the expand/collapse functionality, changes would likely need to be made to the UI code that generates the nodes table. This could involve adding a UI component for the expand/collapse functionality and then tying that component's state to the visibility of the child nodes in the table.

Please provide more details about how you envision this feature working, such as whether you'd like the expand/collapse state to be saved between sessions, or if there are specific requirements for how the expanded/collapsed state should be displayed. This will help in understanding the scope of the changes required and in planning the implementation.

Sources

• flyteadmin/pkg/repositories/models/node_execution.go

---

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.