@ea-lab/reactive-json-docs 0.6.0 → 0.8.0

package/public/rjbuild/docs/core/element/special/ReactiveJsonSubroot.yaml

@@ -145,19 +145,19 @@ renderView:
       1. **Automatic synchronization**: Data remains consistent between parent and subroot
       2. **Simplicity**: No need to manually manage update callbacks
       3. **Performance**: Avoids unnecessary re-renders by propagating directly to the right level
-             4. **Flexibility**: Supports different referencing patterns (~~., ~., ~>) and arrays containing references
+      4. **Flexibility**: Supports different referencing patterns (~~., ~., ~>) and arrays containing references
 
       ### Supported vs Unsupported Cases
 
-      #### ✅ Supported cases
+      #### Supported cases
 
-      ##### 1. Direct reference
+      ##### Direct reference
       ```yaml
       dataOverride: ~~.user
       # Modifications in the subroot propagate to "user" in the parent
       ```
 
-      ##### 2. Object mapping with references
+      ##### Object mapping with references
       ```yaml
       dataOverride:
         userInfo: ~~.user
@@ -166,19 +166,19 @@ renderView:
       # Modifications to "settings" propagate to "config" in the parent
       ```
 
-      ##### 3. Local references
+      ##### Local references
       ```yaml
       dataOverride: ~.localData
       # Modifications propagate to the local template context
       ```
 
-      ##### 4. Hierarchical references
+      ##### Hierarchical references
       ```yaml
       dataOverride: ~>key.someData
       # Modifications propagate up the template hierarchy
       ```
 
-      ##### 5. Arrays in dataOverride
+      ##### Arrays in dataOverride
       ```yaml
       dataOverride:
         - ~~.firstItem
@@ -186,7 +186,7 @@ renderView:
       # Array items with template references are properly handled
       ```
 
-      #### ❌ Unsupported cases
+      #### Unsupported cases
 
       ##### Nested references in data
       ```yaml
@@ -240,7 +240,7 @@ renderView:
               padding: "1rem"
               border: "2px solid #007bff"
               borderRadius: "8px"
-              backgroundColor: "#f8f9fa"
+              
               marginBottom: "1rem"
           content:
             - type: h4
@@ -262,7 +262,7 @@ renderView:
                       padding: "1rem"
                       border: "2px solid #28a745"
                       borderRadius: "8px"
-                      backgroundColor: "#e8f5e9"
+                      
                   content:
                     - type: h4
                       content: "Subroot Editor (with sharedUpdates)"
@@ -306,7 +306,7 @@ renderView:
                   padding: "1rem"
                   border: "1px solid #ddd"
                   borderRadius: "4px"
-                  backgroundColor: "#f5f5f5"
+                  
               content:
                 - type: h5
                   content: "Profile Data"
@@ -320,7 +320,7 @@ renderView:
                   padding: "1rem"
                   border: "1px solid #ddd"
                   borderRadius: "4px"
-                  backgroundColor: "#f5f5f5"
+                  
               content:
                 - type: h5
                   content: "Settings Data"
@@ -346,7 +346,7 @@ renderView:
                     padding: "1rem"
                     border: "2px solid #17a2b8"
                     borderRadius: "8px"
-                    backgroundColor: "#e3f2fd"
+                    
                 content:
                   - type: div
                     content:
@@ -386,7 +386,6 @@ renderView:
               padding: "1rem"
               border: "1px solid #ddd"
               borderRadius: "4px"
-              backgroundColor: "#f9f9f9"
               marginBottom: "1rem"
           content:
             - type: h4
@@ -410,7 +409,6 @@ renderView:
                       padding: "1rem"
                       border: "2px solid #ffc107"
                       borderRadius: "8px"
-                      backgroundColor: "#fff3cd"
                   content:
                     - type: h4
                       content: "Array Items Editor"

package/public/rjbuild/docs/core/element/special/Switch.md

@@ -1,32 +1,30 @@
 # Switch
 
-## Introduction
-
 The `Switch` component allows you to render a list or collection of items using a template, with support for dynamic data, options, and pagination. It is useful for displaying arrays, lists, or collections where each item can be rendered with a specific template or configuration.
 
 ## Properties
-- `content` (array/object, required): The data or path to the data to iterate over
-- `options` (object, optional): Mapping of keys to templates for rendering each item (referenced by `load`)
-- `singleOption` (object, optional): Template to use for each item when all items share the same structure (referenced by `load`)
-- `cardinality` (number, optional): Maximum number of items to render (default: unlimited)
-- `paginated` (boolean, optional): Whether to enable pagination (default: false)
-- `paginationProps` (object, optional): Pagination configuration (page size, etc.)
-- `before` (object, optional): Content to render before the list
-- `after` (object, optional): Content to render after the list
-- `contentWrapper` (object, optional): HTML element configuration to wrap the main content (items only, not before/after)
-  - `tag` (string, optional): HTML tag name (default: "div")
-  - `attributes` (object, optional): HTML attributes to apply to the wrapper element (supports template evaluation)
-- `templates` (object, optional): Named templates referenced by `load` in `singleOption` or `options`
+- `content` (array/object, required): The data or path to the data to iterate over.
+- `options` (object, optional): Mapping of keys to templates for rendering each item (referenced by `load`).
+- `singleOption` (object, optional): Template to use for each item when all items share the same structure (referenced by `load`).
+- `cardinality` (number, optional): Maximum number of items to render (default: unlimited).
+- `paginated` (boolean, optional): Whether to enable pagination (default: false).
+- `paginationProps` (object, optional): Pagination configuration (page size, etc.).
+- `before` (object, optional): Content to render before the list.
+- `after` (object, optional): Content to render after the list.
+- `contentWrapper` (object, optional): HTML element configuration to wrap the main content (items only, not before/after).
+  - `tag` (string, optional): HTML tag name (default: "div").
+  - `attributes` (object, optional): HTML attributes to apply to the wrapper element (supports template evaluation).
+- `templates` (object, optional): Named templates referenced by `load` in `singleOption` or `options`.
 
 ## Behavior
-- Iterates over the provided data and renders each item using the specified template(s)
-- If `options` is provided, uses the corresponding template for each key (with `load`)
-- If `singleOption` is provided, uses the template referenced by `load` for all items
-- Supports limiting the number of items with `cardinality`
-- Supports pagination if `paginated` is true
-- Renders optional `before` and `after` content
-- Can wrap the main content (items) with a custom HTML element using `contentWrapper`
-- Templates are defined in the `templates` object and referenced by name
+- Iterates over the provided data and renders each item using the specified template(s).
+- If `options` is provided, uses the corresponding template for each key (with `load`).
+- If `singleOption` is provided, uses the template referenced by `load` for all items.
+- Supports limiting the number of items with `cardinality`.
+- Supports pagination if `paginated` is true.
+- Renders optional `before` and `after` content.
+- Can wrap the main content (items) with a custom HTML element using `contentWrapper`.
+- Templates are defined in the `templates` object and referenced by name.
 
 ## Content Wrapper Feature
 
@@ -46,7 +44,7 @@ The wrapper only affects the main content items and does not interfere with pagi
 
 ## Examples
 
-### 1. Simple usage with `singleOption` (no pagination)
+### Simple usage with `singleOption` (no pagination)
 ```yaml
 renderView:
   - type: Switch
@@ -65,7 +63,7 @@ data:
     - name: "Charlie"
 ```
 
-### 2. Usage with `options` (different templates per key)
+### Usage with `options` (different templates per key)
 ```yaml
 renderView:
   - type: Switch
@@ -94,7 +92,7 @@ data:
         value: 25
 ```
 
-### 3. Usage with `singleOption`, pagination, before/after, and PageControls
+### Usage with `singleOption`, pagination, before/after, and PageControls
 ```yaml
 renderView:
   - type: Switch
@@ -127,7 +125,7 @@ data:
     - value: 10
 ```
 
-### 4. Usage with `contentWrapper` for CSS Grid Layout
+### Usage with `contentWrapper` for CSS Grid Layout
 ```yaml
 renderView:
   - type: Switch
@@ -168,7 +166,7 @@ data:
       description: "Description of product C"
 ```
 
-### 5. Usage with `contentWrapper` for Flexbox Layout
+### Usage with `contentWrapper` for Flexbox Layout
 ```yaml
 renderView:
   - type: Switch
@@ -201,7 +199,7 @@ data:
     - text: "Item 3"
 ```
 
-### 6. Dynamic `contentWrapper` with Template Evaluation
+### Dynamic `contentWrapper` with Template Evaluation
 ```yaml
 renderView:
   - type: Switch
@@ -238,11 +236,11 @@ data:
 ```
 
 ## Limitations
-- The data must be an array or object; strings and numbers are not supported
-- If both `options` and `singleOption` are provided, `singleOption` takes precedence
-- No built-in support for filtering or sorting (use DataFilter or custom logic)
-- Pagination requires the `paginated` property to be set to true
-- Templates must be defined in the `templates` object and referenced by `load`
+- The data must be an array or object; strings and numbers are not supported.
+- If both `options` and `singleOption` are provided, `singleOption` takes precedence.
+- No built-in support for filtering or sorting (use DataFilter or custom logic).
+- Pagination requires the `paginated` property to be set to true.
+- Templates must be defined in the `templates` object and referenced by `load`.
 
 ### Data Structure Requirements
 Switch requires each item in the data to be an object, not a primitive value:

package/public/rjbuild/docs/core/element/special/Switch.yaml

@@ -6,24 +6,61 @@ renderView:
       The `Switch` component allows you to render a list or collection of items using a template, with support for dynamic data, options, and pagination. It is useful for displaying arrays, lists, or collections where each item can be rendered with a specific template or configuration.
 
       ## Properties
-      - `content` (object/array/string, required): The data or path to the data to iterate over
-      - `options` (object, optional): Mapping of keys to templates for rendering each item (used for object/array of objects)
-      - `singleOption` (object, optional): Template to use for each item when all items share the same structure
-      - `cardinality` (number, optional): Maximum number of items to render (default: unlimited)
-      - `paginated` (boolean, optional): Whether to enable pagination (default: false)
-      - `paginationProps` (object, optional): Pagination configuration (page size, etc.)
-      - `before` (object, optional): Content to render before the list
-      - `after` (object, optional): Content to render after the list
-      - `contentWrapper` (object, optional): HTML element configuration to wrap the main content (items only, not before/after)
-        - `tag` (string, optional): HTML tag name (default: "div")
-        - `attributes` (object, optional): HTML attributes to apply to the wrapper element (supports template evaluation)
 
+  - type: DefinitionList
+    content:
+      - term:
+          code: content
+          after: "(object|array|string, required)"
+        details:
+          type: Markdown
+          content: "Data or path to the data to iterate over."
+      - term:
+          code: options
+          after: "(object, optional)"
+        details: "Mapping of keys to templates for rendering each item (used for object/array of objects)."
+      - term:
+          code: singleOption
+          after: "(object, optional)"
+        details: "Template to use for each item when all items share the same structure."
+      - term:
+          code: cardinality
+          after: "(number, optional)"
+        details: "Maximum number of items to render (default: unlimited)."
+      - term:
+          code: paginated
+          after: "(boolean, optional)"
+        details: "Whether to enable pagination (default: false)."
+      - term:
+          code: paginationProps
+          after: "(object, optional)"
+        details: "Pagination configuration (page size, etc.)."
+      - term:
+          code: before
+          after: "(object, optional)"
+        details: "Content to render before the list."
+      - term:
+          code: after
+          after: "(object, optional)"
+        details: "Content to render after the list."
+      - term:
+          code: contentWrapper
+          after: "(object, optional)"
+        details:
+          type: Markdown
+          content: |
+            HTML element configuration to wrap the main content (items only, not before/after):
+            - `tag` (string, optional): HTML tag name (default: `div`)
+            - `attributes` (object, optional): HTML attributes to apply to the wrapper element (supports template evaluation)
+
+  - type: Markdown
+    content: |
       ## Behavior
-      - Iterates over the provided data and renders each item using the specified template(s)
-      - If `options` is provided, uses the corresponding template for each key
-      - If `singleOption` is provided, uses the same template for all items
-      - Supports limiting the number of items with `cardinality`
-      - Supports pagination if `paginated` is true
+      - Iterates over the provided data and renders each item using the specified template(s).
+      - If `options` is provided, uses the corresponding template for each key.
+      - If `singleOption` is provided, uses the same template for all items.
+      - Supports limiting the number of items with `cardinality`.
+      - Supports pagination if `paginated` is true.
       - Renders optional `before` and `after` content
       - Can wrap the main content (items) with a custom HTML element using `contentWrapper`
 
@@ -88,7 +125,7 @@ renderView:
       ```
 
   - type: RjBuildDescriber
-    title: "1. Simple usage with `singleOption` (no pagination)"
+    title: "Simple usage with `singleOption` (no pagination)"
     description: |
       This example shows a basic Switch rendering a list of users with a single template.
     toDescribe:
@@ -108,7 +145,7 @@ renderView:
           - name: "Charlie"
 
   - type: RjBuildDescriber
-    title: "2. Usage with `options` (different templates per key)"
+    title: "Usage with `options` (different templates per key)"
     description: |
       This example shows how to use different templates for each key in the data.
     toDescribe:
@@ -139,7 +176,7 @@ renderView:
               value: 25
 
   - type: RjBuildDescriber
-    title: "3. Usage with `singleOption` and pagination (4 per page, 10 items)"
+    title: "Usage with `singleOption` and pagination (4 per page, 10 items)"
     description: |
       This example demonstrates pagination with 4 items per page and 10 items in total. PageControls is added to the end of the list.
     toDescribe:
@@ -173,7 +210,7 @@ renderView:
           - value: 10
 
   - type: RjBuildDescriber
-    title: "4. Usage with `contentWrapper` for CSS Grid Layout"
+    title: "Usage with `contentWrapper` for CSS Grid Layout"
     description: |
       This example demonstrates how to use contentWrapper to apply a CSS Grid layout to the Switch items.
     toDescribe:
@@ -239,7 +276,7 @@ renderView:
             description: "Affordable product D"
 
   - type: RjBuildDescriber
-    title: "5. Usage with `contentWrapper` and Pagination"
+    title: "Usage with `contentWrapper` and Pagination"
     description: |
       This example shows how contentWrapper works seamlessly with pagination.
     toDescribe:
@@ -288,7 +325,7 @@ renderView:
           - title: "Card 7"
 
   - type: RjBuildDescriber
-    title: "6. Dynamic `contentWrapper` with Template Evaluation"
+    title: "Dynamic `contentWrapper` with Template Evaluation"
     description: |
       This example demonstrates how contentWrapper attributes can use template evaluation to create dynamic layouts.
     toDescribe:

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

@@ -1,7 +1,5 @@
 # addData
 
-## Introduction
-
 `addData` is a reaction that allows adding data at a specified path in the application's data context. It's particularly useful for appending new items to arrays or adding new properties to objects.
 
 ## Properties

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

@@ -6,9 +6,24 @@ renderView:
       `addData` is a reaction that allows adding data at a specified path in the application's data context. It's particularly useful for appending new items to arrays or adding new properties to objects.
 
       ## Properties
-      - `path` (string, required): The location where the data should be added (using template path syntax with `~` or `~~`). If the path does not exist, it will be created automatically.
-      - `value` (any, optional): The data to add. Can be any valid JSON value (string, number, object, array).
 
+  - type: DefinitionList
+    content:
+      - term:
+          code: path
+          after: "(string, required)"
+        details:
+          type: Markdown
+          content: "The location where the data should be added (using template path syntax with `~` or `~~`). If the path does not exist, it will be created automatically"
+      - term:
+          code: value
+          after: "(any, optional)"
+        details:
+          type: Markdown
+          content: "The data to add. Can be any valid JSON value (string, number, object, array)"
+
+  - type: Markdown
+    content: |
       ## Behavior
       - If the path doesn't exist, it will be created automatically
       - For arrays, the value is appended to the end

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

@@ -1,6 +1,5 @@
 # Reactive-JSON fetchData Documentation
 
-## Introduction
 `fetchData` is a reaction that allows making HTTP requests to a server. It operates in multiple modes, depending on configuration values.
 
 - Supports configurable HTTP methods (GET by default for backward compatibility)
@@ -9,11 +8,11 @@
 - 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.
+- `url` (string, required): The URL to call (must be a static string, dynamic URLs are not supported)
 
 ## Behavior
 - Supports configurable HTTP methods (GET by default for backward compatibility)

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

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.