Skip to content

Reset the noEmitForJsFiles option when updating compiler options #12570

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

Merged
merged 4 commits into from
Nov 30, 2016

Conversation

zhengbli
Copy link
Contributor

No description provided.

@@ -636,6 +636,9 @@ namespace ts.server {
this.cachedUnresolvedImportsPerFile.clear();
this.lastCachedUnresolvedImportsList = undefined;
}
if (this.projectKind === ProjectKind.Inferred || this.projectKind === ProjectKind.Configured) {
Copy link
Contributor

Choose a reason for hiding this comment

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

This piece of code is similar to one in constructor - can you share it?

@vladima
Copy link
Contributor

vladima commented Nov 30, 2016

Can you add tests?

@zhengbli zhengbli force-pushed the resetNoEmitForJsFiles branch from 6af0600 to b0c8a19 Compare November 30, 2016 04:26
const diagsAfterUpdate = session.executeCommand(<server.protocol.CompilerOptionsDiagnosticsRequest>{
type: "request",
command: server.CommandNames.CompilerOptionsDiagnosticsFull,
seq: 3,
Copy link
Member

Choose a reason for hiding this comment

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

I assume the "seq" number should increment with each request. You repeat "3" here (and also in the test below).

@@ -266,6 +264,12 @@ namespace ts.server {
this.markAsDirty();
}

setInternalCompilerOptionsForEmittingJsFiles() {
Copy link
Contributor

Choose a reason for hiding this comment

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

private

@billti
Copy link
Member

billti commented Nov 30, 2016

Thanks @zhengbli . If we put this in the next VS RC, we'll need just this change off of the current commit in the package. Can you create a new branch (e.g. vs/release-2.1) off of commit 5108285 and apply just this change?

@zhengbli
Copy link
Contributor Author

zhengbli commented Nov 30, 2016

Sure, working on it.

Edit: one minute, let me do a final round of local testing to be sure no surprise again.

@zhengbli zhengbli merged commit dfe45fe into microsoft:release-2.1 Nov 30, 2016
@zhengbli zhengbli deleted the resetNoEmitForJsFiles branch November 30, 2016 06:31
@zhengbli
Copy link
Contributor Author

@billti I created https://github.com/Microsoft/TypeScript/tree/vs/release-2.1 that has the changes in this PR. Thank you!

zhengbli added a commit to zhengbli/TypeScript that referenced this pull request Nov 30, 2016
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants