memoryNotificationStores — @gj-kit/nest-notifications
@gj-kit/nest-notifications/testing에서 공개하는 function입니다. package version 0.1.1의 release declaration을 그대로 표시합니다.
검증된 import 예제
섹션 제목: “검증된 import 예제”import { memoryNotificationStores } from '@gj-kit/nest-notifications/testing';시그니처, 매개변수, 반환 타입
섹션 제목: “시그니처, 매개변수, 반환 타입”/** * Never use in production: no durability, no cross-process atomicity, and a * snapshot API that would expose every recipient's content. * * It implements the same `stage`, `tombstoneRecipient` and `registerEndpoint` * seams a host wires over its own adapters, so our own unit suite and a host's * conformance run enter through one door (design 5.4). Row locking is modelled * with a promise chain per outbox row, which is what makes the L1/L2 interleaving * cases mean anything here. */declare function memoryNotificationStores(runtime?: NotificationRuntime): MemoryNotificationStores;이 선언은 매개변수, optionality, 제네릭, 반환값, 공개 union/type 계약의 정본입니다. 호출 전 필요한 환경·권한·오류 경계는 패키지 Golden path와 이 subpath의 import 조건을 함께 확인하세요.
Release context
섹션 제목: “Release context”- 패키지:
@gj-kit/nest-notifications - 버전:
0.1.1 - 공개 entry:
./testing - 소스: GitHub
구현 주석
섹션 제목: “구현 주석”Never use in production: no durability, no cross-process atomicity, and a snapshot API that would expose every recipient’s content.
It implements the same stage, tombstoneRecipient and registerEndpoint
seams a host wires over its own adapters, so our own unit suite and a host’s
conformance run enter through one door (design 5.4). Row locking is modelled
with a promise chain per outbox row, which is what makes the L1/L2 interleaving
cases mean anything here.