@larksuiteoapi/node-sdk 1.3.0 → 1.4.1

package/README.md

@@ -403,7 +403,7 @@ const resule = await dispatcher.invoke(data);
 server.sendResult(result);
 ````
 
-#### challenge校验
+#### Challenge check
 When configuring the event request address, The Open Platform will push a POST request in `application/json` format to the request address. The POST request is used to verify the validity of the configured request address, and the request body will carry a `challenge` field , **The application needs to return the received challenge value to the Open Platform within 1 second**. See: [ Document](https://open.feishu.cn/document/ukTMukTMukTM/uYDNxYjL2QTM24iN0EjN/event-subscription-configure-/request-url-configuration-case)
 
 The adapter provided by the sdk above encapsulates the verification logic. Set the `autoChallenge` field in the options parameter to true to enable:
@@ -430,19 +430,26 @@ router.post(
 ```
 
 ### [Message Card](https://open.feishu.cn/document/ukTMukTMukTM/uczM3QjL3MzN04yNzcDN)
+
 The processing of the Message Card is also a kind of Event processing. The only difference between the two is that the processor of the Message Card is used to respond to the events generated by the interaction between the user and the Message Card. If the processor has a return value (*the value structure should be in line with the structure defined by [Message Card Structure](https://open.feishu.cn/document/ukTMukTMukTM/uEjNwUjLxYDM14SM2ATN)*), then the return value is used to update the responded message card:
 
 ```typescript
 import http from 'http';
 import * as lark from '@larksuiteoapi/node-sdk';
+import type { InteractiveCardActionEvent, InteractiveCard } from '@larksuiteoapi/node-sdk';
 
 const cardDispatcher = new lark.CardActionHandler(
     {
       encryptKey: 'encrypt key',
       verificationToken: 'verification token'
     },
-    async(data) => {
+    async (data: InteractiveCardActionEvent) => {
         console.log(data);
+        const newCard: InteractiveCard = {
+          // your new interactive card content
+          header: {},
+          elements: []
+        };
         return newCard;
     }
 );
@@ -451,6 +458,7 @@ const server = http.createServer();
 server.on('request', lark.adaptDefault('/webhook/card', cardDispatcher));
 server.listen(3000);
 ````
+
 #### `CardActionHandler` construction parameters
 
 | Parameter | Description | Type | Required | Default |

package/README.zh.md

@@ -429,19 +429,26 @@ router.post(
 ```
 
 ### [消息卡片](https://open.feishu.cn/document/ukTMukTMukTM/uczM3QjL3MzN04yNzcDN)
+
 对消息卡片的处理亦是对事件处理的一种，两者的不同点仅在于消息卡片的处理器用于响应用户与消息卡片交互所产生的事件，若处理器有返回值（*返回值的数据结构理应为符合[消息卡片结构](https://open.feishu.cn/document/ukTMukTMukTM/uEjNwUjLxYDM14SM2ATN)所定义的结构*），则返回值被用来更新被响应的消息卡片：
 
 ```typescript
 import http from 'http';
 import * as lark from '@larksuiteoapi/node-sdk';
+import type { InteractiveCardActionEvent, InteractiveCard } from '@larksuiteoapi/node-sdk';
 
 const cardDispatcher = new lark.CardActionHandler(
     {
       encryptKey: 'encrypt key',
       verificationToken: 'verification token'
     },
-    async (data) => {
+    async (data: InteractiveCardActionEvent) => {
         console.log(data);
+        const newCard: InteractiveCard = {
+          // your new interactive card content
+          header: {},
+          elements: []
+        };
         return newCard;
     }
 );
@@ -450,6 +457,7 @@ const server = http.createServer();
 server.on('request', lark.adaptDefault('/webhook/card', cardDispatcher));
 server.listen(3000);
 ```
+
 #### `CardActionHandler`构造参数
 
 |  参数   | 描述  | 类型 | 必须 | 默认 |