MemoryStoreEvent — @gj-kit/toss-payments-postgresql

A public interface from @gj-kit/toss-payments-postgresql/testing. The signature below is taken directly from the 0.5.1 release declaration.

Verified import example

import { MemoryStoreEvent } from '@gj-kit/toss-payments-postgresql/testing';

Signature, parameters, and return type

interface MemoryStoreEvent {
    readonly type: 'store';
    readonly store: MemoryStoreName;
    /**
     * Method name as invoked on that store or on the locked-mutation handle. Store methods that
     * delegate to the handle (`billingKeys.save` / `delete` / `replaceAndGetPrevious` / the two
     * conditional methods) are logged once, under the handle method of the same name — so the
     * core `billingKeys.delete(request)` appears as `delete`, not `deleteIfBillingKeyMatches`.
     */
    readonly operation: string;
    /** Lookup key only — orderId, customerKey, ticketId, dedupeKey, audit id. Never a secret. */
    readonly recordId: string;
    /**
     * Boolean outcome of conditional operations, or a short outcome label — the claim state for
     * `webhookDedupe.claim`, `inserted` / `idempotent` / `conflict` for `orders.saveOrder`,
     * `inserted` / `duplicate` for `audit.record` (same-id re-calls are idempotent like the
     * PostgreSQL sink's `ON CONFLICT (id) DO NOTHING`).
     */
    readonly result?: boolean | string;
}

This declaration is the source of truth for parameters, optionality, generics, return values, and public union/type contracts. Check the package golden path and this subpath’s import conditions for required environment, permission, and error boundaries before calling it.

Release context

• Package: @gj-kit/toss-payments-postgresql
• Version: 0.5.1
• Public entry: ./testing
• Source: GitHub