/** * Email API response interfaces. * All responses use the IApiEnvelope wrapper defined in communication.ts. * * These are the data-shape types that live in brightchain-lib so both * frontend and backend can consume them. The Express-specific wrappers * (extending Response) live in brightchain-api-lib. * * Note: The underlying email interfaces (IEmailMetadata, ISendEmailResult, * IEmailContent, IInboxResult, IDeliveryReceipt) are not currently generic * over TId/TData. When those interfaces gain generic parameters in the future, * these response types should be updated to thread them through. * * Requirements: 12.1, 12.2 */ import { IEmailContent, IInboxResult, ISendEmailResult } from '../../services/messaging/emailMessageService'; import { IApiEnvelope } from '../communication'; import { IDeliveryReceipt } from '../messaging/emailDelivery'; import { IEmailMetadata } from '../messaging/emailMetadata'; export interface ISendEmailResultSerialized extends Omit { deliveryStatus: Record; } export type ISendEmailResponse = IApiEnvelope; export type IReplyToEmailResponse = IApiEnvelope; export type IForwardEmailResponse = IApiEnvelope; export type IGetEmailResponse = IApiEnvelope; export type IGetEmailContentResponse = IApiEnvelope; export type IGetEmailThreadResponse = IApiEnvelope; export type IQueryInboxResponse = IApiEnvelope; export type IGetUnreadCountResponse = IApiEnvelope<{ unreadCount: number; }>; export type IDeleteEmailResponse = IApiEnvelope<{ deleted: boolean; }>; export type IMarkAsReadResponse = IApiEnvelope<{ markedAsRead: boolean; }>; export type IGetDeliveryStatusResponse = IApiEnvelope>; //# sourceMappingURL=emailResponses.d.ts.map