Skip to main content
Version: v0.0.10

Variable: TELECOM_WARNING_MESSAGES

const TELECOM_WARNING_MESSAGES: Readonly<Record<TelecomWarningCode, string>>

The frozen message registry: one fixed sentence per Telecom warning code, and the only source a warning's message can come from.

This is the mechanism, not a convention. telecomWarning takes no value parameter at all, so there is no interpolation site for wire bytes to reach. A Telecom transmission is PHI-dense in almost every field, and a message that quoted so much as a segment code could quote an NDC or a prescription number instead the moment a field separator went missing. What a consumer needs to locate the problem travels in the code and the TelecomPosition: a byte offset and, when known, a 2-character field identifier.

Example

import { TELECOM_WARNING_CODES, TELECOM_WARNING_MESSAGES } from "@cosyte/ncpdp/telecom";
TELECOM_WARNING_MESSAGES[TELECOM_WARNING_CODES.UNKNOWN_SEGMENT];
// "The segment at this offset declares a code this parser does not model; preserved verbatim."