-
Notifications
You must be signed in to change notification settings - Fork 749
feat(stepfunctions): Add a setting to opt out of WFS + minor changes #6501
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -146,6 +146,11 @@ | |
| "default": true, | ||
| "description": "%AWS.stepFunctions.asl.format.enable.desc%" | ||
| }, | ||
| "aws.stepfunctions.workflowStudio.enable": { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is this setting being added?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is explained in point 1:
Our team (including the UX) decided that since custom editor is opened by default, we want to provide a way for the user to opt out of it |
||
| "type": "boolean", | ||
| "default": true, | ||
| "description": "%AWS.stepFunctions.workflowStudio.enable.desc%" | ||
| }, | ||
| "aws.stepfunctions.asl.maxItemsComputed": { | ||
| "type": "number", | ||
| "default": 5000, | ||
|
|
@@ -1412,6 +1417,11 @@ | |
| "command": "aws.openInApplicationComposer", | ||
| "when": "isFileSystemResource && !(resourceFilename =~ /^.*\\.tc\\.json$/) && resourceFilename =~ /^.*\\.(json|yml|yaml|template)$/", | ||
| "group": "z_aws@1" | ||
| }, | ||
| { | ||
| "command": "aws.stepfunctions.openWithWorkflowStudio", | ||
| "when": "isFileSystemResource && resourceFilename =~ /^.*\\.asl\\.(json|yml|yaml)$/", | ||
| "group": "z_aws@1" | ||
| } | ||
| ], | ||
| "view/item/context": [ | ||
|
|
@@ -3838,6 +3848,16 @@ | |
| } | ||
| } | ||
| }, | ||
| { | ||
| "command": "aws.stepfunctions.openWithWorkflowStudio", | ||
| "title": "%AWS.command.stepFunctions.openWithWorkflowStudio%", | ||
| "category": "%AWS.title%", | ||
| "cloud9": { | ||
| "cn": { | ||
| "category": "%AWS.title.cn%" | ||
| } | ||
| } | ||
| }, | ||
| { | ||
| "command": "aws.createNewThreatComposer", | ||
| "title": "%AWS.command.threatComposer.createNew%", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use
workbench.editorAssociations. We already do something similar for threat composer:aws-toolkit-vscode/packages/toolkit/package.json
Lines 4412 to 4415 in 30face9
Do not add new, custom ways of setting file associations.