Skip to content

@codesoul-co/hypha-adapters-local / sqlite-execution-store-foundation

Using this module

Use the Sqlite execution store foundation module for persisting and reading data at this boundary. It exports 1 class.

Import from the package entrypoint

ts
import {
  SQLiteExecutionStoreError,
} from '@codesoul-co/hypha-adapters-local';

Usage patterns

  • The module exposes 1 class as constructable runtime implementations. Each symbol entry lists its constructor and public methods.

Public exports

SymbolKindSignatureDescription
SQLiteExecutionStoreErrorclassnew SQLiteExecutionStoreError(code: SQLiteExecutionStoreFoundationErrorCode, message: string, details?: Record<string, unknown> | undefined, cause?: unknown): SQLiteExecutionStoreFoundationErrorSQLite Execution Store Error class with 10 public constructor or member entries; its exact declarations are listed below.

SQLiteExecutionStoreError

SQLite Execution Store Error class with 10 public constructor or member entries; its exact declarations are listed below.

Declaration

text
export declare class SQLiteExecutionStoreFoundationError extends Error {
    readonly code: SQLiteExecutionStoreFoundationErrorCode;
    readonly details?: Record<string, unknown> | undefined;
    constructor(code: SQLiteExecutionStoreFoundationErrorCode, message: string, details?: Record<string, unknown> | undefined, cause?: unknown);
}

Public members

MemberKindSignatureDescription
causepropertycause?: unknownPublic property; its type, readonly modifier and optionality are shown in the signature.
codepropertyreadonly code: SQLiteExecutionStoreFoundationErrorCodePublic property; its type, readonly modifier and optionality are shown in the signature.
constructorconstructor(code: SQLiteExecutionStoreFoundationErrorCode, message: string, details?: Record<string, unknown> | undefined, cause?: unknown): SQLiteExecutionStoreFoundationErrorCreates an instance of this class.
detailspropertyreadonly details?: Record<string, unknown>Public property; its type, readonly modifier and optionality are shown in the signature.
messagepropertymessage: stringPublic property; its type, readonly modifier and optionality are shown in the signature.
namepropertyname: stringPublic property; its type, readonly modifier and optionality are shown in the signature.
stackpropertystack?: stringPublic property; its type, readonly modifier and optionality are shown in the signature.
static captureStackTracemethodstatic captureStackTrace(targetObject: object, constructorOpt?: Function): voidCreates a .stack property on targetObject, which when accessed returns a string representing the location in the code at which Error.captureStackTrace() was called. js const myObject = {}; Error.captureStackTrace(myObject); myObject.stack; // Similar to `new Error().stack` The first line of the trace will be prefixed with ${myObject.name}: ${myObject.message}. The optional constructorOpt argument accepts a function. If given, all frames above constructorOpt, including constructorOpt, will be omitted from the generated stack trace. The constructorOpt argument is useful for hiding implementation details of error generation from the user. For instance: js function a() { b(); } function b() { c(); } function c() { // Create an error without stack trace to avoid calculating the stack trace twice. const { stackTraceLimit } = Error; Error.stackTraceLimit = 0; const error = new Error(); Error.stackTraceLimit = stackTraceLimit; // Capture the stack trace above function b Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace throw error; } a();
static prepareStackTracemethodstatic prepareStackTrace(err: Error, stackTraces: NodeJS.CallSite[]): anyPublic method; parameters and return type are shown in the signature.
static stackTraceLimitpropertystatic stackTraceLimit: numberThe Error.stackTraceLimit property specifies the number of stack frames collected by a stack trace (whether generated by new Error().stack or Error.captureStackTrace(obj)). The default value is 10 but may be set to any valid JavaScript number. Changes will affect any stack trace captured after the value has been changed. If set to a non-number value, or set to a negative number, stack traces will not capture any frames.