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

Syntax errors are not reported when powershell.scriptAnalysis.enable is set to false #388

Closed
adbertram opened this issue Dec 16, 2016 · 2 comments
Assignees
Labels
Issue-Bug A bug to squash.
Milestone

Comments

@adbertram
Copy link
Contributor

Please fill in these details so that we can help you!

System Details

  • Operating system name and version: macOS sierra
  • VS Code version: 1.8
  • PowerShell extension version: 0.7.2
  • Output from $PSVersionTable: PSv6 alpha 13

Issue Description

It seems that Code no longer can detect problems in my scripts. I can make a number of edits that would prevent the script from compiling and Code never detects them.

Attached Logs

Logs sent to David.

@daviwil daviwil modified the milestone: 0.8.1 Dec 16, 2016
@daviwil
Copy link
Contributor

daviwil commented Dec 17, 2016

Ok, there might be a bug here, I don't see any markers being sent back to the editor for syntax errors in the file. I suspect it's because you've got the powershell.scriptAnalysis.enable: "false" setting in your config file. This shouldn't stop syntax errors from being reported. There was a change in that area of the code recently, I think it might have broken syntax error reporting when Script Analyzer is off.

@daviwil daviwil added the Issue-Bug A bug to squash. label Dec 17, 2016
@daviwil daviwil changed the title Not recognizing syntax errors or extremely slow to do so Syntax errors are not reported when powershell.scriptAnalysis.enable is set to false Dec 17, 2016
@kapilmb kapilmb self-assigned this Dec 17, 2016
@kapilmb
Copy link

kapilmb commented Dec 17, 2016

It is caused by this. We actually return the syntax markers from a downstream method which never gets called if analysis is disabled. I already have a fix in a branch on the PSES repo but I'll wait till a pending PR is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug A bug to squash.
Projects
None yet
Development

No branches or pull requests

3 participants