/** * Feishu message `content`: how an authored body becomes one, and how big one * may be. * * A reply is an interactive card holding one `markdown` element with the * authored Markdown as written. A card is the presentation because the * client shows card text in its compact size; a native post shows the same * text larger. Card Markdown renders the authored `Name` * mention tag as it is, so nothing here rewrites the body. * * The only reason a body is ever cut is size. The budget is measured on the * serialized `content` string, JSON escaping included, because that is what * the platform receives. */ /** * The serialized-content budget for one message, under the platform's * documented 30 KB ceiling. One budget covers rendered and raw cards alike: * they are the same `content` field. */ export declare const FEISHU_MESSAGE_CONTENT_SAFE_BYTES: number; /** * Serialize one authored body into the card contents to send, in order. The * whole body is tried first: a body that fits is one message no matter how * many Markdown blocks it holds. */ export declare function cardContents(body: string): string[]; export declare function assertMessageContentFits(content: string): void; //# sourceMappingURL=message-content.d.ts.map