-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Create a new API to retrieve interpreter details with the ability to cache the details #1567
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
Create a new API to retrieve interpreter details with the ability to cache the details #1567
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1567 +/- ##
=========================================
Coverage ? 71.42%
=========================================
Files ? 277
Lines ? 12983
Branches ? 2334
=========================================
Hits ? 9273
Misses ? 3574
Partials ? 136
Continue to review full report at Codecov.
|
That's quite the title 😉 |
Didn't want anyone to waste time reviewing the PR. However I wanted the This PR is something I was working on during my free time (was getting too tired with debugger). Related to #1351 (laying the ground work for that and a couple of other parts of the extension). |
fca4cf0
to
90ee001
Compare
@Microsoft/pvsc-team This PR is ready for review. |
946e3aa
to
4a6581a
Compare
4a6581a
to
9c35848
Compare
Fixes #1569
Partial work for #1351
This PR introduced about to get interpreter info and cache it. The information built will be used to build the display name and used in analysis engine (separate PR).
So, this PR focuses on being backwards compatible.
This pull request: