@wix/evalforge-evaluator 0.179.0 → 0.181.0

package/build/types/api-client.d.ts

@@ -54,6 +54,27 @@ export interface ApiClientOptions {
      */
     httpClient?: IHttpClient;
 }
+/**
+ * Resolve the `baseURL` for the ambassador `HttpClient` from the configured
+ * `serverUrl`.
+ *
+ * The ambassador request factories emit fully-qualified gateway paths that
+ * already include the `/_api/evalforge-backend` prefix (e.g.
+ * `/_api/evalforge-backend/v1/projects/{id}/eval-runs/{id}`). `serverUrl` also
+ * carries that prefix — it is the REST base `putJson` uses for the one
+ * remaining legacy write (`updateEvalRun`) — so using it directly as the
+ * HttpClient `baseURL` duplicates the prefix
+ * (`.../_api/evalforge-backend/_api/evalforge-backend/v1/...`) and every
+ * ambassador call 404s: the run starts but the evaluator can't fetch its data,
+ * so the eval fails with no results.
+ *
+ * Returning the origin only keeps the ambassador-emitted path intact while the
+ * REST `updateEvalRun` write keeps using the full `serverUrl`. Origin-only
+ * inputs (the local in-cluster `http://host:port`) are returned unchanged.
+ *
+ * @param serverUrl - Base URL of the server (e.g., "https://bo.wix.com/_api/evalforge-backend")
+ */
+export declare function resolveAmbassadorBaseUrl(serverUrl: string): string;
 /**
  * Create an API client for the eval server.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/evalforge-evaluator",
-  "version": "0.179.0",
+  "version": "0.181.0",
   "description": "EvalForge Evaluator",
   "bin": "./build/index.js",
   "files": [
@@ -71,5 +71,5 @@
       "artifactId": "evalforge-evaluator"
     }
   },
-  "falconPackageHash": "ec6cd7242df122dacec1fb89f46734131adb2f8a98afb93362b7bef7"
+  "falconPackageHash": "493d50fade4c488a41b6d072b1d1b500cc4c7dea4090888d9e34ac38"
 }