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

Swap entire project to command palette experience #61

Merged
merged 4 commits into from
Nov 11, 2022
Merged

Conversation

OliverMKing
Copy link
Contributor

Description

Swaps the entire project to the command palette experience.

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

.vsix was tested and checked off by Ahmed and Quentin across a number of systems and scenarios. Unit tests for things that are possible.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

* add draft dockerfile command

* add file

* fix context stuff

* add wizard

* add wizard

* add draft cmd

* add open files step

* add save state step

* add validation

* add run draft dockerfile experience

* add open docs link

* add validation test

* refactor port to common

* add ns

* fix application name guess

* add image validation

* add choose image from acr options

* add override check

* add draft execute

* add open files

* remove hardcoded audience

* refactor logic into create client fn

* default to local folder

* refactor

* swap to async opts

* add extra comment

* remove empty file

* wrap error message

* swap to fs path

* fix back bug

* revert version

* swap to fs path

* remove other commands

* fix typos
Copy link
Member

@Tatsinnit Tatsinnit left a comment

Choose a reason for hiding this comment

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

☕️💡🙏 Thanks @qpetraroia for FYI, added very high level quick eyeball comments. Rest folks who are more involved might be able to add more into the PR, thank you all.

@@ -27,28 +25,20 @@
"properties": {
"aks.draft.releaseTag": {
"type": "string",
"default": "v0.0.22",
Copy link
Member

Choose a reason for hiding this comment

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

💡 Package version update could be part of release PR not the code PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you for review!

Aligned on the package version update being part of the release PR. There's not package version update happening in this PR currently.

The quoted text is the pinned Draft version tag which needs to be bumped in this PR since we are relying on features from new Draft versions.

"group": "draftnavigation@2"
},
Copy link
Member

Choose a reason for hiding this comment

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

💡 Thank you @qpetraroia for quick conversation, since this is removing whole lot of existing functionality, shall we open a tracking issue against repo and Pin it as a breaking change for anyone or 1000 users using this extension in current state. Just an Idea I thought I will FYI.

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for the review @Tatsinnit, yes that is something we will be doing! Documentation and a pinned issue will be created/merged before this change goes live

createNamespace(name: string): Promise<Errorable<void>>;
applyManifests(manifestPaths: string[]): Promise<Errorable<string>>;
applyKustomize(kustomizationDirectory: string): Promise<Errorable<string>>;
installHelm(chartDirectory: string): Promise<Errorable<string>>;
Copy link
Member

Choose a reason for hiding this comment

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

💡 just fyi - please do check, If we have taken dependency on Kubernetes extension I think helm install comes with it, so installing helm at this extension might not be needed. Thanks.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Aligned on that! We do take dependency on the Kubernetes extension and we do get the Helm install from them. You are completely correct.

@qpetraroia
Copy link
Contributor

Hold off on merge until docs and pinned issue is created

@Tatsinnit Tatsinnit requested a review from a team November 10, 2022 00:14
@Tatsinnit Tatsinnit added the enhancement New feature or request label Nov 10, 2022
Copy link
Contributor Author

@OliverMKing OliverMKing left a comment

Choose a reason for hiding this comment

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

I looked through everything and it looks good to me. Everything here has already been reviewed by other people when it was merged into this branch.

@OliverMKing OliverMKing merged commit 87d18f4 into main Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants