Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(stepfunctions): Custom editor to view and edit ASL files - tracer bullet #5613

Open
wants to merge 1 commit into
base: feature/stepfunctions-workflow
Choose a base branch
from

Conversation

witness-me
Copy link

Problem

ASL files, represented as *.asl.json and *.asl.yaml, are rendered using the default JSON editor

Solution

Use existing SFN visual custom editor in VSCode to render ASL files in a visual builder, similar to how it would be displayed in SFN console in create/edit modes.

Current pull request is a tracer bullet implementation without support for local file editing - this functionality will be added in the following changes


License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@witness-me witness-me requested a review from a team as a code owner September 17, 2024 19:03
Copy link

This pull request modifies files 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.

Copy link

This pull request modifies a feature or fixes a bug, but it does not include a changelog entry. All pull requests that introduce new features or bug fixes must have a corresponding changelog item describing the changes.

@witness-me witness-me changed the title feat(StepFunctions): Custom editor to view and edit ASL files - tracer bullet feat(stepfunctions): Custom editor to view and edit ASL files - tracer bullet Sep 17, 2024
@witness-me witness-me changed the base branch from master to feature/stepfunctions-workflow September 17, 2024 19:14
Copy link

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.

Copy link

This pull request implements a feature or fix, so it must include a changelog entry. See CONTRIBUTING.md#changelog for instructions.

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.

4 participants