Merge branch 'github_develop' into develop

Author: lvhuichao

client/packages/openblocks/src/comps/comps/tableComp/tableComp.tsx

@@ -420,6 +420,17 @@ TableTmpComp = withMethodExposing(TableTmpComp, [
       }
     },
   },
+  {
+    method:{
+      name: "resetSelections",
+      description: "",
+      params: [],
+    },
+    execute: (comp) => {
+      comp.children.selection.children.selectedRowKey.dispatchChangeValueAction("0");
+      comp.children.selection.children.selectedRowKeys.dispatchChangeValueAction([]);
+    },
+  },
 ]);
 
 // exposing data

docs/.gitbook/assets/Add a library (1) (1) (1) (1) (1) (1) (1) (1).png

@@ -2,7 +2,7 @@
 
 In Openblocks, event handlers are responsible for collecting and processing events from components and queries, and executing subsequent actions. For example, for a **Button** component, you can add an event handler to trigger the **Run query** action **** in response to the button **Click** event.
 
-<figure><img src="../.gitbook/assets/image (8) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (19).png" alt=""><figcaption></figcaption></figure>
 
 Set event handlers wisely to provide a reactive and responsive user experience (UX). For example, triggering a **get-all** query after **insert-new-data** query finishes enables table automatically refresh.
 
@@ -32,7 +32,7 @@ Running a query can result in success or failure, so queries have two events: **
 
 There are a number of event handler actions available in Openblocks for handling different scenarios. Set them in the **Action** dropdown list in an event handler.
 
-![](<../.gitbook/assets/image (9) (1).png>)
+![](<../.gitbook/assets/image (1) (1).png>)
 
 {% hint style="info" %}
 See [advanced](event-handlers.md#advanced) on this page to know advanced settings.
@@ -48,7 +48,7 @@ Trigger the selected query.
 
 To control a component, select a component in the **Component** dropdown list and call one of its methods in the **Method** dropdown list.
 
-![](<../.gitbook/assets/image (29).png>)
+![](<../.gitbook/assets/image (17).png>)
 
 ### Set temporary state
 

docs/.gitbook/assets/Import on Workspace-level libraries (1) (1) (1) (1) (1) (1) (1).png

@@ -4,7 +4,7 @@ When building an app, you want to reuse components and queries across different
 
 <figure><img src="../.gitbook/assets/module-1.png" alt=""><figcaption><p>Build a <a href="module.md#demo-a-statistics-module">statistics module</a></p></figcaption></figure>
 
-<figure><img src="../.gitbook/assets/module-2 (1).png" alt=""><figcaption><p>Reuse this module anywhere</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/module-2.png" alt=""><figcaption><p>Reuse this module anywhere</p></figcaption></figure>
 
 ## Module basics
 
@@ -67,7 +67,7 @@ Module inputs are parameters passed to the module from external apps. The suppor
 
 This section guides you through the steps to build a statistics module and reuse it in an app. &#x20;
 
-<figure><img src="../.gitbook/assets/module-2 (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../.gitbook/assets/module-2.png" alt=""><figcaption></figcaption></figure>
 
 1.  Create module inputs:
 
@@ -86,7 +86,7 @@ This section guides you through the steps to build a statistics module and reuse
     <figure><img src="../.gitbook/assets/module-17.png" alt=""><figcaption></figcaption></figure>
 5.  Reuse the module multiple times by passing different input values.&#x20;
 
-    <figure><img src="../.gitbook/assets/module-2 (1).png" alt=""><figcaption></figcaption></figure>
+    <figure><img src="../.gitbook/assets/module-2.png" alt=""><figcaption></figcaption></figure>
 
 #### Input Test