@ea-lab/reactive-json-docs 0.7.0 → 1.0.0-alpha.0

package/public/rjbuild/docs/core/reaction/fetchData.yaml

@@ -3,21 +3,50 @@ renderView:
     content: |
       # fetchData
 
-      fetchData is a reaction that allows making HTTP requests to a server. It operates in two distinct modes:
+      `fetchData` is a reaction that allows making HTTP requests to a server. It operates in multiple modes, depending on configuration values.
 
-      The behavior depends on `refreshAppOnResponse`:
-      - If `true` (default): Response must be a valid rjbuild (with renderView/templates/data) as it will be used to re-render the application
-      - If `false`: Response is completely ignored - useful for webhook-like calls or server notifications
-
-      **Important**: Dynamic URLs are not supported. URLs must be static strings.
+      - Supports configurable HTTP methods (GET by default for backward compatibility)
+      - Only one request can be active at a time
+      - The URL is evaluated via the template system before sending, but must resolve to a static string
+      - The response can refresh the app (default) or be ignored
 
       ## Properties
-      - `url` (string, required): The URL to call (must be a static string, dynamic URLs are not supported)
-      - `httpMethod` (string, optional): The HTTP method to use (default: "get"). Supports: get, post, put, patch, delete, etc.
-      - `refreshAppOnResponse` (boolean, optional): If true (default), the response will update the application. If false, the response is ignored (webhook mode).
-      - `updateOnlyData` (boolean, optional): When true and `refreshAppOnResponse` is true, only updates the data section instead of replacing the entire RjBuild. Preserves templates and renderView. Default: false.
-      - `updateDataAtLocation` (string, optional): When `updateOnlyData` is true, specifies where to place the response data using template path syntax (e.g., "~~.userProfile", "~.config.settings"). If not specified, replaces the entire data object.
 
+  - type: DefinitionList
+    content:
+      - term:
+          code: httpMethod
+          after: "(string, optional)"
+        details:
+          type: Markdown
+          content: "The HTTP method to use (default: \"get\"). Supports: get, post, put, patch, delete, etc."
+      - term:
+          code: refreshAppOnResponse
+          after: "(boolean, optional)"
+        details:
+          type: Markdown
+          content: "If true (default), the response will update the application. If false, the response is ignored (webhook mode)"
+      - term:
+          code: updateDataAtLocation
+          after: "(string, optional)"
+        details:
+          type: Markdown
+          content: "When `updateOnlyData` is true, specifies where to place the response data using template path syntax (e.g., \"~~.userProfile\", \"~.config.settings\"). If not specified, replaces the entire data object"
+      - term:
+          code: updateOnlyData
+          after: "(boolean, optional)"
+        details:
+          type: Markdown
+          content: "When true and `refreshAppOnResponse` is true, only updates the data section instead of replacing the entire RjBuild. Preserves templates and renderView. Default: false"
+      - term:
+          code: url
+          after: "(string, required)"
+        details:
+          type: Markdown
+          content: "The URL to call (must be a static string, dynamic URLs are not supported)"
+
+  - type: Markdown
+    content: |
       ## Behavior
       - Supports configurable HTTP methods (GET by default for backward compatibility)
       - Only one request can be active at a time
@@ -176,12 +205,22 @@ renderView:
           content:
             - type: div
               attributes:
-                class: "col-md-6"
+                style:
+                  width: "48%"
+                  display: "inline-block"
+                  verticalAlign: "top"
+                  marginRight: "2%"
               content:
                 - type: BsButton
                   content: "Complete Data Replacement"
                   attributes:
-                    class: "btn btn-primary mb-2 w-100"
+                    style:
+                      padding: "8px 16px"
+                      margin: "8px 0"
+                      border: "1px solid #007bff"
+                      borderRadius: "4px"
+                      cursor: "pointer"
+                      width: "100%"
                   actions:
                     - what: fetchData
                       on: click
@@ -197,12 +236,22 @@ renderView:
             
             - type: div
               attributes:
-                class: "col-md-6"
+                style:
+                  width: "48%"
+                  display: "inline-block"
+                  verticalAlign: "top"
+                  marginRight: "2%"
               content:
                 - type: BsButton
                   content: "Targeted Data Update"
                   attributes:
-                    class: "btn btn-secondary mb-2 w-100"
+                    style:
+                      padding: "8px 16px"
+                      margin: "8px 0"
+                      border: "1px solid #6c757d"
+                      borderRadius: "4px"
+                      cursor: "pointer"
+                      width: "100%"
                   actions:
                     - what: fetchData
                       on: click
@@ -224,7 +273,11 @@ renderView:
             - type: BsButton
               content: "🔄 Reset to Initial Data"
               attributes:
-                class: "btn btn-secondary"
+                style:
+                  padding: "8px 16px"
+                  border: "1px solid #6c757d"
+                  borderRadius: "4px"
+                  cursor: "pointer"
               actions:
                 - what: fetchData
                   on: click
@@ -240,7 +293,11 @@ renderView:
           content:
             - type: div
               attributes:
-                class: "col-md-4"
+                style:
+                  width: "32%"
+                  display: "inline-block"
+                  verticalAlign: "top"
+                  marginRight: "1%"
               content:
                 - type: h6
                   content: "👤 User Profile"
@@ -266,7 +323,11 @@ renderView:
             
             - type: div
               attributes:
-                class: "col-md-4"
+                style:
+                  width: "32%"
+                  display: "inline-block"
+                  verticalAlign: "top"
+                  marginRight: "1%"
               content:
                 - type: h6
                   content: "⚙️ Settings"
@@ -292,7 +353,11 @@ renderView:
             
             - type: div
               attributes:
-                class: "col-md-4"
+                style:
+                  width: "32%"
+                  display: "inline-block"
+                  verticalAlign: "top"
+                  marginRight: "1%"
               content:
                 - type: h6
                   content: "📊 Status"

package/public/rjbuild/docs/core/reaction/moveData.md

@@ -1,13 +1,9 @@
 # Reaction: moveData
 
-## Introduction
-
 The `moveData` reaction changes the position of an element within an array in the global data context. This is particularly useful for reordering items in a list, for example, moving an item up or down. Like `removeData`, it can operate in `path` mode or `target` mode.
 
 ## Properties
 
-- `what` (string, required): The name of the reaction, which must be `moveData`.
-- `on` (string, required): The name of the event that triggers the reaction.
 - `path` (string, optional): The path to the array element to move. Required if `target` is not used.
 - `target` (string, optional): If set to `currentTemplateData`, the reaction will target the data associated with the current template item.
 - `parentLevel` (number, optional): Used with `target: 'currentTemplateData'`. Specifies how many levels to go up from the current data path to find the element to move.

package/public/rjbuild/docs/core/reaction/moveData.yaml

@@ -7,13 +7,35 @@ renderView:
 
       ## Properties
 
-      - `what` (string, required): The name of the reaction, which must be `moveData`.
-      - `on` (string, required): The name of the event that triggers the reaction.
-      - `path` (string, optional): The path to the array element to move. Required if `target` is not used.
-      - `target` (string, optional): If set to `currentTemplateData`, the reaction will target the data associated with the current template item.
-      - `parentLevel` (number, optional): Used with `target: 'currentTemplateData'`. Specifies how many levels to go up from the current data path to find the element to move.
-      - `increment` (integer, required): The number of positions to move the element. A positive integer moves it down (towards the end of the array), and a negative integer moves it up (towards the beginning).
+  - type: DefinitionList
+    content:
+      - term:
+          code: path
+          after: "(string, optional)"
+        details:
+          type: Markdown
+          content: "The path to the array element to move. Required if `target` is not used"
+      - term:
+          code: target
+          after: "(string, optional)"
+        details:
+          type: Markdown
+          content: "If set to `currentTemplateData`, the reaction will target the data associated with the current template item"
+      - term:
+          code: parentLevel
+          after: "(number, optional)"
+        details:
+          type: Markdown
+          content: "Used with `target: 'currentTemplateData'`. Specifies how many levels to go up from the current data path to find the element to move"
+      - term:
+          code: increment
+          after: "(integer, required)"
+        details:
+          type: Markdown
+          content: "The number of positions to move the element. A positive integer moves it down (towards the end of the array), and a negative integer moves it up (towards the beginning)"
 
+  - type: Markdown
+    content: |
       ## Behavior
 
       - When triggered, `moveData` repositions an element within an array.

package/public/rjbuild/docs/core/reaction/postMessage.md

@@ -1,13 +1,9 @@
 # Reaction: postMessage
 
-## Introduction
-
 The `postMessage` reaction sends a message to another window or frame using the standard `window.postMessage` Web API. This is useful for communication between your Reactive-JSON application and a parent window (if embedded in an iframe) or for other cross-origin communication scenarios.
 
 ## Properties
 
-- `what` (string, required): The name of the reaction, must be `postMessage`.
-- `on` (string, required): The event that triggers the reaction (e.g., `click`, `change`).
 - `message` (any, required): The data to send as the message. This value is evaluated and can be any serializable type (string, number, object, array).
 - `messageTarget` (string, optional): The target window for the message. Can be `'parent'` (the default) or `'self'`.
 - `targetOrigin` (string, optional): Specifies the origin of the target window for security. Defaults to the current window's origin (`window.location.origin`). Use `"*"` for any origin, but be aware of the security implications.

package/public/rjbuild/docs/core/reaction/postMessage.yaml

@@ -17,13 +17,36 @@ renderView:
   - type: Markdown
     content: |
       ## Properties
-      - `what` (string, required): The name of the reaction, must be `postMessage`.
-      - `on` (string, required): The event that triggers the reaction (e.g., `click`, `change`).
-      - `message` (any, required): The data to send as the message. This value is evaluated and can be any serializable type (string, number, object, array).
-      - `messageTarget` (string, optional): The target window for the message. Can be `'parent'` (the default) or `'self'`.
-      - `targetOrigin` (string, optional): Specifies the origin of the target window for security. Defaults to the current window's origin (`window.location.origin`). Use `"*"` for any origin, but be aware of the security implications.
-      - `includeChangedValue` (boolean, optional): If the trigger event is `change` on an input element, setting this to `true` will add the input's new value to the message payload under the key `changedValue`. Currently, this is only supported for checkboxes.
 
+  - type: DefinitionList
+    content:
+      - term:
+          code: message
+          after: "(any, required)"
+        details:
+          type: Markdown
+          content: "The data to send as the message. This value is evaluated and can be any serializable type (string, number, object, array)"
+      - term:
+          code: messageTarget
+          after: "(string, optional)"
+        details:
+          type: Markdown
+          content: "The target window for the message. Can be 'parent' (the default) or 'self'"
+      - term:
+          code: targetOrigin
+          after: "(string, optional)"
+        details:
+          type: Markdown
+          content: "Specifies the origin of the target window for security. Defaults to the current window's origin (`window.location.origin`). Use \"*\" for any origin, but be aware of the security implications"
+      - term:
+          code: includeChangedValue
+          after: "(boolean, optional)"
+        details:
+          type: Markdown
+          content: "If the trigger event is `change` on an input element, setting this to `true` will add the input's new value to the message payload under the key `changedValue`. Currently, this is only supported for checkboxes"
+
+  - type: Markdown
+    content: |
       ## Behavior
       - When triggered, the reaction evaluates the `message` content.
       - It identifies the target window based on `messageTarget` and the target origin from `targetOrigin`.

package/public/rjbuild/docs/core/reaction/redirectNow.md

@@ -1,13 +1,9 @@
 # Reaction: redirectNow
 
-## Introduction
-
 The `redirectNow` reaction performs an immediate browser redirection to a specified URL. It is useful for navigating to a new page after an action is completed, such as after submitting a form or clicking a link.
 
 ## Properties
 
-- `what` (string, required): The name of the reaction, which must be `redirectNow`.
-- `on` (string, required): The name of the event that triggers the reaction (e.g., `click`).
 - `to` (string, required): The URL to redirect to. This value is evaluated, so it can be a static URL or dynamically constructed from data.
 
 ## Behavior

package/public/rjbuild/docs/core/reaction/redirectNow.yaml

@@ -7,10 +7,17 @@ renderView:
 
       ## Properties
 
-      - `what` (string, required): The name of the reaction, which must be `redirectNow`.
-      - `on` (string, required): The name of the event that triggers the reaction (e.g., `click`).
-      - `to` (string, required): The URL to redirect to. This value is evaluated, so it can be a static URL or dynamically constructed from data.
+  - type: DefinitionList
+    content:
+      - term:
+          code: to
+          after: "(string, required)"
+        details:
+          type: Markdown
+          content: "The URL to redirect to. This value is evaluated, so it can be a static URL or dynamically constructed from data"
 
+  - type: Markdown
+    content: |
       ## Behavior
 
       - When triggered, the reaction evaluates the `to` property to get the target URL.

package/public/rjbuild/docs/core/reaction/removeData.md

@@ -1,13 +1,9 @@
 # Reaction: removeData
 
-## Introduction
-
 The `removeData` reaction deletes data from a specific location in the global data context. It is essential for dynamically managing lists, removing items, or clearing parts of the application state. It can operate in two modes: `path` mode (to target a specific data location) or `target` mode (to target the current template's data).
 
 ## Properties
 
-- `what` (string, required): The name of the reaction, which must be `removeData`.
-- `on` (string, required): The name of the event that triggers the reaction (e.g., `click`).
 - `path` (string, optional): The target location in the data context to delete. Required if `target` is not used.
 - `target` (string, optional): If set to `currentTemplateData`, the reaction will remove the data associated with the current template item.
 - `parentLevel` (number, optional): Used with `target: 'currentTemplateData'`. Specifies how many levels to go up from the current data path before removing. `0` means the current level.
@@ -22,7 +18,7 @@ The `removeData` reaction deletes data from a specific location in the global da
 
 ## Examples
 
-### 1. Using `path` to remove a specific key
+### Using `path` to remove a specific key
 
 This example shows how to delete a specific user profile field by clicking a button.
 
@@ -42,7 +38,7 @@ data:
     email: "john.doe@example.com"
 ```
 
-### 2. Using `target` to remove an item from a list
+### Using `target` to remove an item from a list
 
 This example shows a list of users where each user can be removed by clicking a "Remove" button next to their name. The reaction targets the current item in the iteration.
 

package/public/rjbuild/docs/core/reaction/removeData.yaml

@@ -5,8 +5,46 @@ renderView:
 
       The `removeData` reaction deletes data from a specific location in the global data context. It can operate in two modes: `path` mode or `target` mode.
 
+      ## Properties
+
+  - type: DefinitionList
+    content:
+      - term:
+          code: path
+          after: "(string, optional)"
+        details:
+          type: Markdown
+          content: "Path to the data to remove. Required if `target` is not used"
+      - term:
+          code: target
+          after: "(string, optional)"
+        details:
+          type: Markdown
+          content: "If set to `currentTemplateData`, the reaction will target the data associated with the current template item"
+      - term:
+          code: parentLevel
+          after: "(number, optional)"
+        details:
+          type: Markdown
+          content: "Used with `target: 'currentTemplateData'`. Specifies how many levels to go up from the current data path before removing. `0` means the current level"
+
+  - type: Markdown
+    content: |
+      ## Behavior
+
+      - When triggered, `removeData` deletes the data at the specified location.
+      - **Path Mode**: Uses the `path` property to identify what to remove.
+      - **Target Mode**: Uses `target: 'currentTemplateData'` to remove the current template data item from its parent array.
+      - The reaction has no effect if the target data doesn't exist.
+
+      ## Limitations
+
+      - Either `path` or `target` must be specified.
+      - With `target` mode, the data must be part of an array for removal to work.
+      - Removing non-existent data has no effect (no error is thrown).
+
   - type: RjBuildDescriber
-    title: "1. Using `path` to remove a specific key"
+    title: "Using `path` to remove a specific key"
     description: "This example shows how to delete a specific user profile field by clicking a button."
     toDescribe:
       renderView:
@@ -24,7 +62,7 @@ renderView:
           email: "john.doe@example.com"
 
   - type: RjBuildDescriber
-    title: "2. Using `target` to remove an item from a list"
+    title: "Using `target` to remove an item from a list"
     description: |
       This example shows a list of users where each user can be removed by clicking a "Remove" button next to their name.
       The reaction uses `target: currentTemplateData` to identify which item to remove from the list.

package/public/rjbuild/docs/core/reaction/setClipboardData.md

@@ -1,13 +1,9 @@
 # Reaction: setClipboardData
 
-## Introduction
-
 The `setClipboardData` reaction copies a specified value to the user's clipboard. This is useful for creating "Copy to clipboard" buttons for sharing information like referral codes, URLs, or any text-based data.
 
 ## Properties
 
-- `what` (string, required): The name of the reaction, which must be `setClipboardData`.
-- `on` (string, required): The name of the event that triggers the reaction (e.g., `click`).
 - `value` (any, required): The value to be copied to the clipboard. The value is evaluated, so it can be a literal string or a path to data.
 
 ## Behavior

package/public/rjbuild/docs/core/reaction/setClipboardData.yaml

@@ -7,10 +7,17 @@ renderView:
 
       ## Properties
 
-      - `what` (string, required): The name of the reaction, which must be `setClipboardData`.
-      - `on` (string, required): The name of the event that triggers the reaction (e.g., `click`).
-      - `value` (any, required): The value to be copied to the clipboard. The value is evaluated, so it can be a literal string or a path to data.
+  - type: DefinitionList
+    content:
+      - term:
+          code: value
+          after: "(any, required)"
+        details:
+          type: Markdown
+          content: "The value to be copied to the clipboard. The value is evaluated, so it can be a literal string or a path to data"
 
+  - type: Markdown
+    content: |
       ## Behavior
 
       - When triggered, the reaction evaluates the `value` property.

package/public/rjbuild/docs/core/reaction/setData.md

@@ -1,13 +1,9 @@
 # Reaction: setData
 
-## Introduction
-
 The `setData` reaction updates the data at a specific location in the global data context. It is one of the most fundamental reactions for managing state and making applications interactive. It can be used to set simple values, objects, or the result of a template evaluation.
 
 ## Properties
 
-- `what` (string, required): The name of the reaction, which must be `setData`.
-- `on` (string, required): The name of the event that triggers the reaction (e.g., `click`, `change`).
 - `path` (string, required): The target location in the data context where the value will be set. It supports `~.` notation for relative paths.
 - `value` (any, required): The value to set at the specified path. This value is evaluated, so it can be a literal, a path to other data, or a template string.
 - **Conditional properties** (optional): Like all reactions, `setData` supports conditional execution using `when`, `is`, `isNot`, `isEmpty`, `contains`, `>`, `<`, `>=`, `<=`, `andConditions`, `orConditions`.
@@ -56,10 +52,24 @@ This example shows how to use conditions with `setData` to only execute when cer
 
 ```yaml
 renderView:
-  - type: TextField
-    dataLocation: ~.username
-    label: "Username:"
-    placeholder: "Enter username"
+  - type: label
+    content: "Username:"
+  - type: input
+    attributes:
+      type: "text"
+      value: ~.username
+      placeholder: "Enter username"
+      style:
+        padding: "8px"
+        margin: "8px 0"
+        border: "1px solid #ccc"
+        borderRadius: "4px"
+        width: "200px"
+    actions:
+      - what: setData
+        on: input
+        path: ~.username
+        value: "<reactive-json:event-new-value>"
   - type: button
     content: "Set Welcome Message"
     actions:

package/public/rjbuild/docs/core/reaction/setData.yaml

@@ -5,14 +5,32 @@ renderView:
 
       The `setData` reaction updates the data at a specific location in the global data context. It is one of the most fundamental reactions for managing state and making applications interactive. It can be used to set simple values, objects, or the result of a template evaluation.
 
-      ### Properties
-      - `what` (string, required): The name of the reaction, which must be `setData`.
-      - `on` (string, required): The name of the event that triggers the reaction (e.g., `click`, `change`).
-      - `path` (string, required): The target location in the data context where the value will be set. It supports `~.` notation for relative paths.
-      - `value` (any, required): The value to set at the specified path. This value is evaluated, so it can be a literal, a path to other data, or a template string.
-      - **Conditional properties** (optional): Like all reactions, `setData` supports conditional execution using `when`, `is`, `isNot`, `isEmpty`, `contains`, `>`, `<`, `>=`, `<=`, `andConditions`, `orConditions`.
+      ## Properties
 
-      ### Behavior
+  - type: DefinitionList
+    content:
+      - term:
+          code: path
+          after: "(string, required)"
+        details:
+          type: Markdown
+          content: "The target location in the data context where the value will be set. It supports `~.` notation for relative paths"
+      - term:
+          code: value
+          after: "(any, required)"
+        details:
+          type: Markdown
+          content: "The value to set at the specified path. This value is evaluated, so it can be a literal, a path to other data, or a template string"
+      - term:
+          code: conditionalProperties
+          after: "(optional)"
+        details:
+          type: Markdown
+          content: "Like all reactions, `setData` supports conditional execution using `when`, `is`, `isNot`, `isEmpty`, `contains`, `>`, `<`, `>=`, `<=`, `andConditions`, `orConditions`"
+
+  - type: Markdown
+    content: |
+      ## Behavior
       - When triggered by the specified event (`on`), `setData` evaluates the `value` property within the current context.
       - It then updates the data at the location specified by `path`.
       - If the `value` is an object or an array, it is deep-cloned before being set to prevent shared-state mutations.
@@ -55,10 +73,24 @@ renderView:
     description: "This example shows how to use conditions with `setData` to only execute when certain criteria are met."
     toDescribe:
       renderView:
-        - type: TextField
-          dataLocation: ~.username
-          label: "Username:"
-          placeholder: "Enter username"
+        - type: label
+          content: "Username:"
+        - type: input
+          attributes:
+            type: "text"
+            value: ~.username
+            placeholder: "Enter username"
+            style:
+              padding: "8px"
+              margin: "8px 0"
+              border: "1px solid #ccc"
+              borderRadius: "4px"
+              width: "200px"
+          actions:
+            - what: setData
+              on: input
+              path: ~.username
+              value: "<reactive-json:event-new-value>"
         - type: button
           content: "Set Welcome Message"
           actions:

package/public/rjbuild/docs/core/reaction/submitData.md

@@ -1,6 +1,5 @@
 # Reactive-JSON submitData Documentation
 
-## Introduction
 `submitData` is a reaction that allows sending data to a server via HTTP requests (usually POST). It's especially useful for form submissions and API interactions.
 
 - The payload can be customized with the `data` property.
@@ -44,7 +43,7 @@ This limitation is intentional to avoid data consistency issues but may be restr
 ### Styling Submitting State (CSS)
 You can visually disable form controls during submission using CSS. There are two main approaches:
 
-#### 1. Target only the submitting control (button, input, etc.)
+#### Target only the submitting control (button, input, etc.)
 The element that triggered the submission receives `data-is-submitting="true"` during the request:
 
 ```css
@@ -58,7 +57,7 @@ textarea[data-is-submitting="true"] {
 }
 ```
 
-#### 2. Target all controls globally during submission
+#### Target all controls globally during submission
 While a submission is in progress, the `<body>` receives `data-html-builder-is-submitting="true"`. You can use this to disable all form controls:
 
 ```css

package/public/rjbuild/docs/core/reaction/submitData.yaml

@@ -10,14 +10,50 @@ renderView:
       - The response can refresh the app (default) or be ignored.
 
       ## Properties
-      - `url` (string, required): The destination URL for the request
-      - `httpMethod` (string, optional): The HTTP method to use (default: "post")
-      - `data` (object, optional): The data to send. If not specified, data is sent in an object with the structure `{ data: globalDataContext.templateData }`. If `__state` exists in the context, it is automatically added.
-      - `refreshAppOnResponse` (boolean, optional): If true (default), reloads the application with the server response. If false, the response is ignored and **no change is made to the application's state or display** (just like `fetchData`).
-      - `submitSilently` (boolean, optional): If true, doesn't apply visual disabling styles during submission
-      - `updateOnlyData` (boolean, optional): When true and `refreshAppOnResponse` is true, only updates the data section instead of replacing the entire RjBuild. Preserves templates and renderView. Default: false.
-      - `updateDataAtLocation` (string, optional): When `updateOnlyData` is true, specifies where to place the response data using template path syntax (e.g., "~~.userProfile", "~.config.settings"). If not specified, replaces the entire data object.
 
+  - type: DefinitionList
+    content:
+      - term:
+          code: url
+          after: "(string, required)"
+        details: "The destination URL for the request"
+      - term:
+          code: httpMethod
+          after: "(string, optional)"
+        details:
+          type: Markdown
+          content: "The HTTP method to use (default: \"post\")"
+      - term:
+          code: data
+          after: "(object, optional)"
+        details:
+          type: Markdown
+          content: "The data to send. If not specified, data is sent in an object with the structure `{ data: globalDataContext.templateData }`. If `__state` exists in the context, it is automatically added"
+      - term:
+          code: refreshAppOnResponse
+          after: "(boolean, optional)"
+        details:
+          type: Markdown
+          content: "If true (default), reloads the application with the server response. If false, the response is ignored and **no change is made to the application's state or display** (just like `fetchData`)"
+      - term:
+          code: submitSilently
+          after: "(boolean, optional)"
+        details: "If true, doesn't apply visual disabling styles during submission"
+      - term:
+          code: updateOnlyData
+          after: "(boolean, optional)"
+        details:
+          type: Markdown
+          content: "When true and `refreshAppOnResponse` is true, only updates the data section instead of replacing the entire RjBuild. Preserves templates and renderView. Default: false"
+      - term:
+          code: updateDataAtLocation
+          after: "(string, optional)"
+        details:
+          type: Markdown
+          content: "When `updateOnlyData` is true, specifies where to place the response data using template path syntax (e.g., \"~~.userProfile\", \"~.config.settings\"). If not specified, replaces the entire data object"
+
+  - type: Markdown
+    content: |
       ## Behavior
       - Only one submission can be active at a time (global lock)
       - The default HTTP method is POST, but can be customized

package/public/rjbuild/docs/core/reaction/triggerEvent.md

@@ -1,13 +1,9 @@
 # Reaction: triggerEvent
 
-## Introduction
-
 The `triggerEvent` reaction programmatically dispatches an event on one or more target elements found via a CSS selector. This allows for indirect interactions, such as one button triggering the `click` event of another element, or simulating user actions on specific components.
 
 ## Properties
 
-- `what` (string, required): The name of the reaction, must be `triggerEvent`.
-- `on` (string, required): The event that triggers this reaction.
 - `eventName` (string, required): The name of the event to dispatch on the target element(s) (e.g., `click`, `focus`).
 - `selector` (string, required): A CSS selector to identify the target element(s) that will receive the event.
 - `selectorBase` (string, optional): Defines the starting point for the `selector` search.