콘텐츠로 이동

notificationRecipientKey — @gj-kit/nest-notifications

@gj-kit/nest-notifications/core에서 공개하는 function입니다. package version 0.1.1의 release declaration을 그대로 표시합니다.

import { notificationRecipientKey } from '@gj-kit/nest-notifications/core';
/**
* Stable opaque key for the recipient liveness barrier. The digest is
* byte-identical to `sha256(applicationKey + U+0000 + recipientRef)`, so a host
* that already stores tombstones under the source's key needs no migration.
*
* Throws `ERR_NOTIFICATION_RECIPIENT_KEY_INPUT` when either input contains a
* U+0000 code point: the separator is only injective while the inputs are free
* of it, and a length-prefixed encoding would have changed the digest (design
* 0.2-5).
*
* The caller is the host, not the pipeline: a
* {@link ../core/lifecycle!NotificationRecipientLiveness} implementation uses it
* as the tombstone row key, which lets the barrier outlive a purge without
* retaining the raw recipient reference.
*/
declare function notificationRecipientKey(applicationKey: string, recipientRef: string): string;

이 선언은 매개변수, optionality, 제네릭, 반환값, 공개 union/type 계약의 정본입니다. 호출 전 필요한 환경·권한·오류 경계는 패키지 Golden path와 이 subpath의 import 조건을 함께 확인하세요.

  • 패키지: @gj-kit/nest-notifications
  • 버전: 0.1.1
  • 공개 entry: ./core
  • 소스: GitHub

Stable opaque key for the recipient liveness barrier. The digest is byte-identical to sha256(applicationKey + U+0000 + recipientRef), so a host that already stores tombstones under the source’s key needs no migration.

Throws ERR_NOTIFICATION_RECIPIENT_KEY_INPUT when either input contains a U+0000 code point: the separator is only injective while the inputs are free of it, and a length-prefixed encoding would have changed the digest (design 0.2-5).

The caller is the host, not the pipeline: a {@link ../core/lifecycle!NotificationRecipientLiveness} implementation uses it as the tombstone row key, which lets the barrier outlive a purge without retaining the raw recipient reference.