Skip to content

Conversation

@zelzhou
Copy link

@zelzhou zelzhou commented Oct 3, 2025

Problem

When starting a new StateMachine execution from the ExecutionDetails tab, currently we do not fill the StartExecution tab with the existing ExecutionInput.

Solution

Auto fill existing ExecutionInput when click StartExecution from ExecutionDetails tab.

Demo

StartExecution

  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@zelzhou zelzhou requested a review from a team as a code owner October 3, 2025 20:29
@github-actions
Copy link

github-actions bot commented Oct 3, 2025

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.

@@ -0,0 +1,4 @@
{
"type": "Feature",
"description": "[Step Functions] Start Execution from Execution Details tab now fills the existing Execution Input in the Start Execution tab."
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we need a new changelog for this since it's not released yet

Copy link
Author

Choose a reason for hiding this comment

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

I thought we need to keep the changelog for every changes even it's unreleased. If not I can remove this entry.

"description": "AWS Contributed Icon",
"default": {
"fontPath": "./resources/fonts/aws-toolkit-icons.woff",
"fontCharacter": "\\f1d0"
Copy link
Contributor

Choose a reason for hiding this comment

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

These changes don't look related, can you remove them?

Copy link
Author

Choose a reason for hiding this comment

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

Yeah this seems like a result of npm instsall. Let me see why this is here and remove it.

Copy link
Author

Choose a reason for hiding this comment

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

Update: it seems like npm install will always bring back this change.

Copy link
Contributor

Choose a reason for hiding this comment

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

We might need to sync changes in the feature branch since it's 600 commits behind. Can you update the feature branch and rebase this change on that?

Copy link
Author

Choose a reason for hiding this comment

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

Yeah I can do a merge from master first.

async created() {
this.initialData = (await client.init()) ?? this.initialData
if (this.initialData.executionInput) {
this.executionInput = this.initialData.executionInput
Copy link
Contributor

Choose a reason for hiding this comment

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

should we auto format it like the console?

Copy link
Author

Choose a reason for hiding this comment

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

It would be nice to add that. Let me see how I can achieve that.

@zelzhou zelzhou closed this Oct 3, 2025
@zelzhou zelzhou deleted the feature/stepfunctions-execution branch October 3, 2025 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants