Skip to content

Bundle Pylance as part of an extension pack (not a hard dependency) - #16077

Merged
Kim-Adeline Miguel (kimadeline) merged 4 commits into
microsoft:default-language-serverfrom
kimadeline:bundle-pylance
May 3, 2021
Merged

Bundle Pylance as part of an extension pack (not a hard dependency)#16077
Kim-Adeline Miguel (kimadeline) merged 4 commits into
microsoft:default-language-serverfrom
kimadeline:bundle-pylance

Conversation

@kimadeline

@kimadeline Kim-Adeline Miguel (kimadeline) commented Apr 29, 2021

Copy link
Copy Markdown

For https://github.com/microsoft/vscode-python-internalbacklog/issues/180

Bundling Pylance as an extension pack (not a hard dependency) at build time. Also, I am bad at naming things, please suggest different names if you can think of something more fitting.

@kimadeline Kim-Adeline Miguel (kimadeline) added no-changelog No news entry required skip package*.json package.json and package-lock.json don't both need updating skip tests Updates to tests unnecessary labels Apr 29, 2021
@kimadeline Kim-Adeline Miguel (kimadeline) changed the title Bundle Pylance as part of an extension pack (not a dependency) Bundle Pylance as part of an extension pack (not a hard dependency) Apr 29, 2021
@kimadeline
Kim-Adeline Miguel (kimadeline) marked this pull request as ready for review April 29, 2021 15:27

@karrtikr Kartik Raj (karrtikr) left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. Do we need to add a news entry?

@kimadeline

Copy link
Copy Markdown
Author

I don't think so, not yet at least. I was going to add a news entry when we update the readme (which should be soon enough).

- run: npm run addExtensionDependencies
shell: bash

- run: npm run addExtensionPackDependencies

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Any reason to use another gulp task rather than just having it be a part of the extension dependencies one?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

I figured we might want to keep them separate since it's messing with a different package.json key.

@kimadeline
Kim-Adeline Miguel (kimadeline) merged commit 85b1a3a into microsoft:default-language-server May 3, 2021
@kimadeline
Kim-Adeline Miguel (kimadeline) deleted the bundle-pylance branch May 3, 2021 20:17
Kim-Adeline Miguel (kimadeline) added a commit that referenced this pull request May 5, 2021
* Bundle Pylance as part of an extension pack (not a hard dependency) (#16077)

   * extension pack
   * Undo package.json change
   * Add extension pack link at build time
   * Forgot to update all names

* Update readme + license at build time (#16134)

* Add license update

* Update package.json description

* Update readme

* Add news file

* Update header wording

* let -> const

* Wording

* Consistenly use VS Code long form

* Display an informational Pylance prompt for existing users (#16069)

* Export extension version memento

* Add localization strings

* Add prompt check

* Add to the list of things triggering on activation

* Add tests

* Rename file

* Remove unsupported newlines

* Fix localization + re-add newlines

* Change to be a non-blocking diagnostic check

* Change localization key

* Update memento on close instead of just on ok

* Fix localization

* Add initialMementoValue handler

* Links

* Fix tests

* Fix tests

* Set PYLANCE_PROMPT_MEMENTO to false

* Remove unused line

* Set to true directly

* Remove extra updateMemento calls

* I can't read

* Period

* Run in foreground

* Add handling test

* Remove extension pack category (#16149)

Co-authored-by: Jake Bailey <5341706+jakebailey@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog No news entry required skip package*.json package.json and package-lock.json don't both need updating skip tests Updates to tests unnecessary

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants