@@ -87,6 +87,35 @@ export class ExtractorMessage {
8787 */
8888 public readonly messageId : tsdoc . TSDocMessageId | ExtractorMessageId | string ;
8989
90+ /**
91+ * If the {@link IExtractorInvokeOptions.messageCallback} sets this property to true, it will prevent the message
92+ * from being displayed by API Extractor.
93+ *
94+ * @remarks
95+ * If the `messageCallback` routes the message to a custom handler (e.g. a toolchain logger), it should
96+ * assign `handled = true` to prevent API Extractor from displaying it. Assigning `handled = true` for all messages
97+ * would effectively disable all console output from the `Extractor` API.
98+ *
99+ * If `handled` is set to true, the message will still be included in the count of errors/warnings;
100+ * to discard a message entirely, instead assign `logLevel = none`.
101+ */
102+ public handled : boolean ;
103+
104+ /**
105+ * Specifies how the message should be reported.
106+ *
107+ * @remarks
108+ * If the {@link IExtractorInvokeOptions.messageCallback} handles the message (i.e. sets `handled = true`),
109+ * it can use the `logLevel` to determine how to display the message.
110+ *
111+ * Alternatively, if API Extractor is handling the message, the `messageCallback` could assign `logLevel` to change
112+ * how it will be processed. However, in general the recommended practice is to configure message routing
113+ * using the `messages` section in api-extractor.json.
114+ *
115+ * To discard a message entirely, assign `logLevel = none`.
116+ */
117+ public logLevel : ExtractorMessageLogLevel ;
118+
90119 /**
91120 * The text description of this issue.
92121 */
0 commit comments