Skip to content

Ensure we can use proposed VS Code API with ts-node - #12038

Merged
Don Jayamanne (DonJayamanne) merged 2 commits into
microsoft:masterfrom
DonJayamanne:fixProposedTypes
May 28, 2020
Merged

Ensure we can use proposed VS Code API with ts-node#12038
Don Jayamanne (DonJayamanne) merged 2 commits into
microsoft:masterfrom
DonJayamanne:fixProposedTypes

Conversation

@DonJayamanne

@DonJayamanne Don Jayamanne (DonJayamanne) commented May 28, 2020

Copy link
Copy Markdown

For #12025
ts-node sucks (things work when using tsc compiler, but not with ts-node).


suite('Data Science - NativeNotebook ContentProvider', () => {
// tslint:disable: no-any
suite('Data Science - NativeNotebook ContentProviderxxx', () => {

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.

Remove xxx for grepping :)

@sonarqubecloud

Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@DonJayamanne
Don Jayamanne (DonJayamanne) merged commit 8c8efb8 into microsoft:master May 28, 2020
@DonJayamanne
Don Jayamanne (DonJayamanne) deleted the fixProposedTypes branch May 28, 2020 18:47
Tim Ruscica (techwithtim) pushed a commit to techwithtim/vscode-python that referenced this pull request May 28, 2020
* Use a proxy type for propsed types (for ts-node)
* Oh yes `ts-node` sucks, cuz it doesn't work the same way as `tsc` compiler
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.

4 participants