@incodetech/core 0.0.0-dev-20260828-40eb3fde → 0.0.0-dev-20260828-b9635cef

package/dist/videoSelfieUploadService-DgQJXRoo.esm.js

@@ -1,86 +0,0 @@
-import { t as api } from "./api-Bx3gKW_y.esm.js";
-import { t as endpoints } from "./endpoints-DmVOhy8C.esm.js";
-//#region src/internal/recordings/videoSelfieUploadService.ts
-/**
-* Origin of the dedicated video-selfie-service (e.g.
-* `https://video-selfie-service.stage.incodetest.com`), set from
-* `setup({ videoSelfie: { apiURL } })`. Testing/special-env override: when
-* unset (production), the upload endpoints resolve against the main `apiURL`
-* and the service mesh (Istio) routes them to the service. The service
-* accepts the same session token; the shared `api` client attaches it either
-* way.
-*/
-let serviceBaseUrl = null;
-function setVideoSelfieServiceUrl(url) {
-	let trimmed = url ?? "";
-	while (trimmed.endsWith("/")) trimmed = trimmed.slice(0, -1);
-	serviceBaseUrl = trimmed || null;
-}
-function uploadUrl(path) {
-	return serviceBaseUrl ? `${serviceBaseUrl}${path}` : path;
-}
-/**
-* Opens a scoped multipart video upload session. Idempotent server-side: if
-* an upload is already in progress for the `(session, scope)` pair, the same `uploadId`
-* comes back along with the parts already stored (`parts` non-empty) — but
-* always with a fresh `epoch` that locks out whoever held the previous one.
-*/
-async function initiateVideoSelfieUpload(scope = "videoselfie") {
-	const response = await api.post(uploadUrl(endpoints.videoSelfieUploadInitiate), void 0, { query: { scope } });
-	return {
-		uploadId: response.data.uploadId,
-		epoch: response.data.epoch,
-		scope,
-		parts: response.data.parts ?? []
-	};
-}
-/**
-* Uploads a single chunk as a multipart part. The body is the raw video bytes
-* (no base64, no client-side encryption — encryption at rest is server-side
-* S3 SSE). Every part except the last must be >= 5 MiB (enforced
-* server-side). Returns the part number + `etag` needed to complete the
-* upload. Rejects with a `409` status when a newer initiate fenced this
-* session out.
-*/
-async function uploadVideoSelfiePart(session, partNumber, chunk) {
-	const response = await api.post(uploadUrl(endpoints.videoSelfieUploadPart), chunk, {
-		query: {
-			uploadId: session.uploadId,
-			epoch: session.epoch,
-			partNumber,
-			scope: session.scope
-		},
-		headers: { "Content-Type": "application/octet-stream" }
-	});
-	return {
-		partNumber: response.data.partNumber,
-		etag: response.data.etag
-	};
-}
-/**
-* Finalizes the upload. The service assembles from the parts it stored; the
-* optional `parts` list is deliberately NOT sent — chunks staged below the
-* S3 minimum are combined and renumbered server-side, so a client-side list
-* could contradict the authoritative one. Safe to repeat if the response
-* was lost. Returns the server-reported status. Rejects with `400` naming a
-* missing part when the sequence has a hole.
-*/
-async function completeVideoSelfieUpload(session) {
-	return (await api.post(uploadUrl(endpoints.videoSelfieUploadComplete), {
-		uploadId: session.uploadId,
-		epoch: session.epoch
-	}, { query: { scope: session.scope } })).data.status;
-}
-/**
-* Discards an in-progress upload and everything already sent for it, so the
-* backend fails the upload straight away instead of waiting for its expiry.
-* Call when a recording is abandoned or its upload can no longer complete.
-*/
-async function abortVideoSelfieUpload(session) {
-	return (await api.post(uploadUrl(endpoints.videoSelfieUploadAbort), {
-		uploadId: session.uploadId,
-		epoch: session.epoch
-	}, { query: { scope: session.scope } })).data.status;
-}
-//#endregion
-export { uploadVideoSelfiePart as a, setVideoSelfieServiceUrl as i, completeVideoSelfieUpload as n, initiateVideoSelfieUpload as r, abortVideoSelfieUpload as t };