Skip to content

This site describes solve-engine as it is on main: 2.43.0, which npm does not have yet. npm installs 2.40.0, so a page may show an answer that version does not give yet.

AsyncCheckResult

Defined in: packages/engine/src/resolvers/ResolverRegistry.ts:13

Result from a resolver’s preflight() check. Returned when async data is needed, the orchestrator uses this to subscribe to the resolver and return a Pending value immediately.

optional metadata?: Record<string, unknown>;

Defined in: packages/engine/src/resolvers/ResolverRegistry.ts:23

Optional metadata for diagnostics


packageId: string;

Defined in: packages/engine/src/resolvers/ResolverRegistry.ts:19

Package owning this resolver


queryKey: string;

Defined in: packages/engine/src/resolvers/ResolverRegistry.ts:15

Unique cache key for deduplication (e.g., “{packageId}:rates:USD:GBP”)


optional refetch?: () => Promise<Value>;

Defined in: packages/engine/src/resolvers/ResolverRegistry.ts:37

Force a fresh fetch of this exact query, bypassing staleTime, and return the new value. Supplied alongside refetchIntervalMs so the engine can drive the background refresh without re-scanning bytecode.

Promise<Value>


optional refetchIntervalMs?: number;

Defined in: packages/engine/src/resolvers/ResolverRegistry.ts:31

Cadence, in ms, at which this value wants proactive background refresh (a live quote every minute, an FX rate every few minutes). Absent, or paired with no refetch, means pull-only: the value refreshes on re-evaluation, never on its own. Only acted on when the host has enabled background refresh; see BackgroundRefreshConfig.


resolver: Promise<Value>;

Defined in: packages/engine/src/resolvers/ResolverRegistry.ts:17

Promise that resolves to the final Value


signal: AbortSignal;

Defined in: packages/engine/src/resolvers/ResolverRegistry.ts:21

AbortSignal for stale-data prevention