From ac5c0eb46d1942e55facbf3230ddd2023c11c2ee Mon Sep 17 00:00:00 2001 From: Johan Ljunggren Date: Wed, 12 Jul 2023 10:22:25 +0200 Subject: [PATCH] SqlServerDsc: Fix workspace settings (#1948) --- .vscode/settings.json | 2 +- CHANGELOG.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/.vscode/settings.json b/.vscode/settings.json index 7ac5819f5..f79c57a39 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -13,7 +13,7 @@ "powershell.codeFormatting.alignPropertyValuePairs": true, "powershell.codeFormatting.useConstantStrings": true, "powershell.developer.bundledModulesPath": "${cwd}/output/RequiredModules", - "powershell.scriptAnalysis.settingsPath": ".vscode/analyzersettings.psd1", + "powershell.scriptAnalysis.settingsPath": "/.vscode/analyzersettings.psd1", "powershell.scriptAnalysis.enable": true, "files.trimTrailingWhitespace": true, "files.trimFinalNewlines": true, diff --git a/CHANGELOG.md b/CHANGELOG.md index 91e869815..0c39b19f0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -20,6 +20,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 - Re-enable integration tests for dbatools. - Bumped dbatools to v2.0.1 for the integration tests. - Running PSScriptAnalyzer on the built module ([issue #1945](https://github.com/dsccommunity/SqlServerDsc/issues/1945)). + - Fix a path in VS Code workspace settings to correctly use Script Analyzer on Linux and macOS. ### Fixed