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

Do not report semantic diagnostics for infered and external projects with only .js files #14716

Merged
merged 1 commit into from
Mar 20, 2017

Conversation

mhegazy
Copy link
Contributor

@mhegazy mhegazy commented Mar 18, 2017

return true;
}
return false;
return (project.projectKind === ProjectKind.Inferred || project.projectKind === ProjectKind.External) && project.isJsOnlyProject();
Copy link
Member

Choose a reason for hiding this comment

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

So if they're using a "configured" project (e.g. a lot of our solutions for issues such as "too much JavaScript" involve adding a tsconfig with "allowJs": true and settings some exclude dirs), will they get semantic diagnostics again? If its a configured project with "allowJs" set and it isJsOnlyProject, then it should also suppress semantic diagnostics.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

correct. if you have configured project the check is false, and the normal checking for semantic errors proceed. this is only if you have external or inferred project, with only .js files.

@mhegazy mhegazy merged commit 238edf0 into master Mar 20, 2017
@mhegazy mhegazy deleted the fix14565 branch March 20, 2017 17:45
@microsoft microsoft locked and limited conversation to collaborators Jun 21, 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