Show workflow outputs in workflow run screen

[wintonzheng]

Important

Add UI section in WorkflowRun.tsx to display workflow outputs in JSON format when run is finalized.

• UI Enhancement:
  • In WorkflowRun.tsx, added a section to display "Block Outputs" using CodeEditor when workflowRunIsFinalized is true.
  • Outputs are shown in JSON format, read-only, with a min height of 96px and max height of 500px.

^{This description was created by for a0936bd. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Incremental review on a0936bd in 9 seconds

More details

• Looked at 25 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. skyvern-frontend/src/routes/workflows/WorkflowRun.tsx:621

• Draft comment:
  Consider adding a null check for workflowRun.outputs before using JSON.stringify to avoid potential errors if outputs is undefined.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR introduces a new UI section to display workflow outputs in JSON format when the workflow run is finalized. The implementation seems correct, but there are a few areas to improve.

Workflow ID: wflow_1BKdoL2O2tEeI8t1

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to a0936bd in 36 seconds

More details

• Looked at 25 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. skyvern-frontend/src/routes/workflows/WorkflowRun.tsx:621

• Draft comment:
  Consider checking if workflowRun.outputs is defined before using JSON.stringify to avoid potential errors.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable:
  The comment is suggesting a potential improvement to avoid runtime errors if workflowRun.outputs is undefined. However, the code already checks if workflowRun is truthy, which reduces the likelihood of workflowRun.outputs being undefined. The comment is speculative and not based on a definite issue, as the code logic seems to handle the case where workflowRun is undefined.
  The comment might be valid if workflowRun.outputs can be undefined even when workflowRun is truthy. However, without evidence of this scenario, the comment remains speculative.
  The comment lacks strong evidence of a definite issue, as the code logic already checks for workflowRun. Without further context or evidence, the comment seems speculative.
  The comment is speculative and not based on a definite issue. It should be deleted as it does not provide strong evidence of a necessary code change.

Workflow ID: wflow_iV0XQIK8VNzD3GBl

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.