-
Notifications
You must be signed in to change notification settings - Fork 751
revert: cloud9 related code #6376
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
Conversation
| These keys are currently set by the core/ package, but many of them may eventually be migrated to | ||
| toolkit/ or amazonq/ if appropriate. | ||
|
|
||
| - `isCloud9`: This is hardcoded by Cloud9 itself, not the Toolkit. |
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.
package.json updates will be a separate PR
Depends on aws#6376
packages/amazonq/package.json
Outdated
| "id": "aws.amazonq.notifications", | ||
| "name": "%AWS.notifications.title%", | ||
| "when": "!isCloud9 && !aws.isSageMaker && aws.amazonq.notifications.show" | ||
| "when": "!aws.isSageMaker && aws.amazonq.notifications.show" |
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.
Anything that applies to sagemaker potentially applies to isCloud9CodeEditor. This looks like such a case.
for now, we can either leave this as isCloud9 and create a backlog issue to revisit the remaining isCloud9 cases like this, or rename it to isCloud9CodeEditor (or whatever we call it)
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.
These seem to be leftover artifacts from notifications development. I have fixed them, but left isCloud9 to revisit later.
| const editCreds = messages.editCredentials(false) | ||
| // TODO: getHelp page for Cloud9. | ||
| const buttons = isCloud9() ? [editCreds] : [editCreds, getHelp] | ||
| const buttons = [editCreds, getHelp] |
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.
seems like something we should either leave or leave a todo comment with a token that we can find later. because we don't want to show vscode-related messaging.
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.
The related link is not vscode related: https://docs.aws.amazon.com/signin/latest/userguide/differences-aws_builder_id.html
The auth story for a Cloud9CodeEditor is unclear though. A todo to verify would be better.
|
|
||
| // Only used in rare cases on C9 | ||
| export const reauth = Commands.declare( | ||
| '_aws.codecatalyst.reauthenticate', |
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.
can we delete the command code?
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.
No because the comment was wrong, it's used here:
| reauth.build(auth.activeConnection, auth).asTreeNode({ |
| } | ||
| } | ||
|
|
||
| // TODO: Delete? as it was only used in Cloud9 |
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.
yeah, we dropped the "quickstart" concept, which had overlap with (1) the marketplace readme, and (2) the new notifications / whats-new concept.
| /** | ||
| * Temporary util while Cloud9 does not have codicon support | ||
| */ | ||
| export function addCodiconToString(codiconName: string, text: string): string { |
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.
might be able to drop this function, maybe a comment that mentions "cloud9" should stay on it
packages/toolkit/.changes/next-release/Removal-3ef48be0-d3f3-4252-be69-9a0684406944.json
Outdated
Show resolved
Hide resolved
11df401 to
2f5215a
Compare
This code removes nearly all cloud9 codepaths: - Icons, readme generation, scripts - ikp3db lambda/sam debugger support - Cloud9 only codepaths and hacks - Docs and comments mentioning Cloud9 Includes some follow up items as TODOs in code. Some items were left in case they are helpful in the future (e.g. for vscode web or similar). The items should be renamed from Cloud9 if used again in the future. Some examples are Cloud9 runtime environment checks (for lambda/sam), `isCloud9()` and properties/text for Cloud9 IDE, some SAM artifacts, don't start LSP server, etc. Search cloud9 in vscode after merging this change.
…252-be69-9a0684406944.json Co-authored-by: Justin M. Keyes <[email protected]>
This code removes nearly all cloud9 codepaths: - Icons, readme generation, scripts - ikp3db lambda/sam debugger support - Cloud9 only codepaths and hacks - Docs and comments mentioning Cloud9 Includes some follow up items as TODOs in code. Some items were left in case they are helpful in the future (e.g. for vscode web or similar). The items should be renamed from Cloud9 if used again in the future. Some examples are Cloud9 runtime environment checks (for lambda/sam), `isCloud9()` and properties/text for Cloud9 IDE, some SAM artifacts, don't start LSP server, etc. Search cloud9 in vscode after merging this change. --- - 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license. --------- Co-authored-by: Justin M. Keyes <[email protected]>
This code removes nearly all cloud9 codepaths: - Icons, readme generation, scripts - ikp3db lambda/sam debugger support - Cloud9 only codepaths and hacks - Docs and comments mentioning Cloud9 Includes some follow up items as TODOs in code. Some items were left in case they are helpful in the future (e.g. for vscode web or similar). The items should be renamed from Cloud9 if used again in the future. Some examples are Cloud9 runtime environment checks (for lambda/sam), `isCloud9()` and properties/text for Cloud9 IDE, some SAM artifacts, don't start LSP server, etc. Search cloud9 in vscode after merging this change. --- - 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license. --------- Co-authored-by: Justin M. Keyes <[email protected]>
This code removes nearly all cloud9 codepaths: - Icons, readme generation, scripts - ikp3db lambda/sam debugger support - Cloud9 only codepaths and hacks - Docs and comments mentioning Cloud9 Includes some follow up items as TODOs in code. Some items were left in case they are helpful in the future (e.g. for vscode web or similar). The items should be renamed from Cloud9 if used again in the future. Some examples are Cloud9 runtime environment checks (for lambda/sam), `isCloud9()` and properties/text for Cloud9 IDE, some SAM artifacts, don't start LSP server, etc. Search cloud9 in vscode after merging this change. --- - 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license. --------- Co-authored-by: Justin M. Keyes <[email protected]>
This code removes nearly all cloud9 codepaths:
Includes some follow up items as TODOs in code.
Some items were left in case they are helpful in the future (e.g. for vscode web or similar). The items should be renamed from Cloud9 if used again in the future. Some examples are Cloud9 runtime environment checks (for lambda/sam),
isCloud9()and properties/text for Cloud9 IDE, some SAM artifacts, don't start LSP server, etc. Search cloud9 in vscode after merging this change.feature/xbranches will not be squash-merged at release time.