Skip to content

Rkeithhill/is122 script analysis profile path #137

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

Conversation

rkeithhill
Copy link
Contributor

This is the vscode extension side of the implementation. There will be a PSES PR to go along with this.


This change is Reviewable

This adds a scriptAnalysis.settingsPath setting but uncovers some issues about how to be an absolute path back to the language host from the client.  Depending on where the user "set" this setting a relative path has a different meaning.  If set in .vscode\settings.json then relative probably should be relative to the workspaceRoot.  In the global settings file, it should probably be the extensionInstallDir.  If in the user's settings file, then what ... their home dir?

If we treated this like the other HostPaths then relative would *always* be relative to the extensionInstallDir.  If we could get VSCode to expand ${workspaceRoot} that would allow the user to specify a path in the current workspace folder.
Use empty string now to get the default (built-in) settings for script analysis.  Tweaked the build script to fix some problems and to exclude the script analysis settings file. Also changed encoding the SampleModule.psd1 file to UTF8.
@daviwil
Copy link
Contributor

daviwil commented Apr 10, 2016

Looks good!

@rkeithhill rkeithhill merged commit 60987b7 into PowerShell:master Apr 10, 2016
@rkeithhill rkeithhill deleted the rkeithhill/is122-scriptAnalysisProfilePath branch April 10, 2016 21:49
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.

3 participants