mirror of
https://github.com/snapotter-hq/SnapOtter.git
synced 2026-08-03 07:46:42 +02:00
fix(passport-photo): require the face-detection bundle, not just background-removal (#329)
* fix(passport-photo): require the face-detection bundle, not just background-removal Passport Photo runs face-landmark detection (face_landmarks.py, gated to the face-detection bundle) before background removal (background-removal bundle), but it was only declared under and guarded against background-removal. A user who installed only Background Removal passed every JS-side check, then hit a late "feature_not_installed" from the Python dispatcher gate when the analyze step ran face landmarks, and the UI never told them Face Detection was needed. - shared: add TOOL_EXTRA_BUNDLES + getRequiredBundlesForTool so a tool can declare more than one required bundle (passport-photo needs background-removal and face-detection). enablesTools is untouched, so the one-tool-per-bundle invariant still holds. - api: isToolInstalled() now checks every required bundle; add getFirstMissingBundleForTool() so the analyze and base routes, pipeline (both guards) and batch report the bundle the user actually still needs. - web: the proactive install prompt (tool-page) and features-store treat a tool as installed only when all required bundles are present, and point the prompt at the first missing one (sequential install, no new UI). Refs #327 * test(passport-photo): deterministic integration coverage for the two-bundle guard Boots the real API with an isolated DATA_DIR and controls installed.json to prove the HTTP route behavior end-to-end: - nothing installed -> 501 naming background-removal - only background-removal installed -> 501 naming face-detection (issue #327) - both installed -> guard passes (not 501) - base route reports face-detection too Refs #327
This commit is contained in:
@@ -18,7 +18,7 @@ import { dirname, join, resolve } from "node:path";
|
||||
import type { Readable } from "node:stream";
|
||||
import { fileURLToPath } from "node:url";
|
||||
import type { FeatureBundleState, FeatureStatus } from "@snapotter/shared";
|
||||
import { FEATURE_BUNDLES, TOOL_BUNDLE_MAP } from "@snapotter/shared";
|
||||
import { FEATURE_BUNDLES, getRequiredBundlesForTool } from "@snapotter/shared";
|
||||
import * as tar from "tar";
|
||||
|
||||
// ── Paths ───────────────────────────────────────────────────────────────
|
||||
@@ -146,9 +146,22 @@ export function isFeatureInstalled(bundleId: string): boolean {
|
||||
}
|
||||
|
||||
export function isToolInstalled(toolId: string): boolean {
|
||||
const bundleId = TOOL_BUNDLE_MAP[toolId];
|
||||
if (!bundleId) return true;
|
||||
return isFeatureInstalled(bundleId);
|
||||
const required = getRequiredBundlesForTool(toolId);
|
||||
if (required.length === 0) return true;
|
||||
return required.every((bundleId) => isFeatureInstalled(bundleId));
|
||||
}
|
||||
|
||||
/**
|
||||
* The first required bundle for a tool that is not yet installed, or null when
|
||||
* the tool needs no bundle or all of them are installed. A tool can require
|
||||
* more than one bundle (see TOOL_EXTRA_BUNDLES), so this is what tells the user
|
||||
* exactly which feature to install next.
|
||||
*/
|
||||
export function getFirstMissingBundleForTool(toolId: string): string | null {
|
||||
for (const bundleId of getRequiredBundlesForTool(toolId)) {
|
||||
if (!isFeatureInstalled(bundleId)) return bundleId;
|
||||
}
|
||||
return null;
|
||||
}
|
||||
|
||||
// ── Install status mutations ────────────────────────────────────────────
|
||||
|
||||
Reference in New Issue
Block a user