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

Use new extensionPack key #563

Merged
merged 3 commits into from
Aug 20, 2018
Merged

Use new extensionPack key #563

merged 3 commits into from
Aug 20, 2018

Conversation

vazexqi
Copy link
Contributor

@vazexqi vazexqi commented Aug 15, 2018

What does this PR do?

See the changes in https://code.visualstudio.com/updates/v1_26#_extension-packs-revisited

What issues does this PR fix or reference?

#562

@vazexqi vazexqi requested a review from lcampos August 15, 2018 12:45
@codecov
Copy link

codecov bot commented Aug 15, 2018

Codecov Report

Merging #563 into develop will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop     #563   +/-   ##
========================================
  Coverage    72.09%   72.09%           
========================================
  Files          155      155           
  Lines         6157     6157           
  Branches       953      953           
========================================
  Hits          4439     4439           
  Misses        1485     1485           
  Partials       233      233

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d2ed065...a0ae946. Read the comment docs.

@@ -28,7 +28,7 @@
"vscode:publish": "node ../../scripts/publish-vsix.js"
},
"categories": ["Extension Packs"],
"extensionDependencies": [
"extensionPack": [
Copy link
Contributor

Choose a reason for hiding this comment

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

Don't we need to update vscode engine version as well ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's a good question. Let me check. I somehow thought it was retroactively applied since this is an extension pack. This is just a key per my understanding.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Confirmed on #562 that we do need to bump up to the latest version.
I think this is OK since our stats indicate that our customers are apt to upgrade to the latest version of VS Code quickly.

@vazexqi vazexqi force-pushed the nick/use-new-extensionpack-key branch from 3cab42a to 54cdae6 Compare August 19, 2018 21:34
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