From 0bdd44176799eae918a2a8f6b0f188e01564b4b2 Mon Sep 17 00:00:00 2001 From: Koen Vlaswinkel Date: Wed, 11 Oct 2023 13:33:24 +0200 Subject: [PATCH] Use `saveBeforeStart` setting when running a variant analysis This will respect the user's `saveBeforeStart` setting when running a variant analysis. This re-uses the existing `saveBeforeStart` function that is used when running local queries. The default behavior if the setting is not set is to save all open named files. --- .../src/variant-analysis/variant-analysis-manager.ts | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/extensions/ql-vscode/src/variant-analysis/variant-analysis-manager.ts b/extensions/ql-vscode/src/variant-analysis/variant-analysis-manager.ts index 411186bb1..8ff46901f 100644 --- a/extensions/ql-vscode/src/variant-analysis/variant-analysis-manager.ts +++ b/extensions/ql-vscode/src/variant-analysis/variant-analysis-manager.ts @@ -42,7 +42,7 @@ import { processVariantAnalysisRepositoryTask, } from "./variant-analysis-processor"; import PQueue from "p-queue"; -import { createTimestampFile } from "../run-queries-shared"; +import { createTimestampFile, saveBeforeStart } from "../run-queries-shared"; import { readFile, remove, pathExists } from "fs-extra"; import { EOL } from "os"; import { cancelVariantAnalysis } from "./gh-api/gh-actions-api-client"; @@ -199,6 +199,8 @@ export class VariantAnalysisManager progress: ProgressCallback, token: CancellationToken, ): Promise { + await saveBeforeStart(); + progress({ maxStep: 5, step: 0,