fix(cli)!: retain repeated WASM input paths (#9624)

BREAKING CHANGE: caller_input_paths values may now be ordered arrays of strings as well as strings. Clients must accept both forms.
This commit is contained in:
morluto authored and GitHub committed 2026-11-09 19:43:01 +08:00
1 parent 8dc2d7bec4
commit 400a91b5f9
7 files changed
+79 -12

No files matched your search

+4 -2
View File
@@ -2,6 +2,7 @@ import {
parseEvidence,
withEvidenceCallerInputPath,
type Evidence,
type CallerInputPaths,
} from "../domain/evidence.js";
import type { AnalysisError } from "../domain/analysisErrorBase.js";
import type { Result } from "../domain/result.js";
@@ -13,7 +14,7 @@ export const bindCliEvidenceCallerPath =
(
callerPath: string,
run: () => Promise<Result<Evidence, AnalysisError>>,
additionalPaths?: Readonly<Record<string, string>>,
additionalPaths?: CallerInputPaths,
): (() => Promise<Result<Evidence, AnalysisError>>) =>
async () => {
const result = await run();
@@ -49,9 +50,10 @@ export const finishCliEvidenceCommand = (
providerId: string,
operation: string,
signal: AbortSignal,
additionalPaths?: CallerInputPaths,
) =>
finishAnalysisCommand(
bindCliEvidenceCallerPath(callerPath, run),
bindCliEvidenceCallerPath(callerPath, run, additionalPaths),
service,
providerId,
operation,