Skip to content

Conversation

daviwil
Copy link
Contributor

@daviwil daviwil commented May 12, 2016

This change is Reviewable

@daviwil
Copy link
Contributor Author

daviwil commented May 12, 2016

@rkeithhill Let me know if I missed anything in the changelog :)


- `powershell.scriptAnalysis.settingsPath`: Specifies the path to a PowerShell Script Analyzer settings file. Use either an absolute path (to override the default settings for all projects) or use a path relative to your workspace.

## 0.5.0
Copy link
Contributor

@rkeithhill rkeithhill May 12, 2016

Choose a reason for hiding this comment

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

  • Added support for new VSCode command Debug: Start Without Debugging. Shortcut for this command is Ctrl+F5.
  • Changed the keyboard shortcut for PowerShell: Expand Alias from Ctrl+F5 to Ctrl+Alt+e.
  • Added support for specifying either a user PSScriptAnalyzer settings file by setting a full path in your User Settings file for the setting powershell.scriptAnalysis.settingsPath. You can also configure this setting in your workspace's .vscode\settings.json file to a workspace relative path. This settings file overrides the one configured in your User Settings file - if it's configured there. See the extension's Examples\.vscode\settings.json file for an example.
@daviwil
Copy link
Contributor Author

daviwil commented May 12, 2016

Thanks Keith! I updated the changelog with your suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants