@ea-lab/reactive-json-docs 2.8.0 → 2.10.0

package/public/rjbuild/docs/getting-started/reactions.md

@@ -71,6 +71,10 @@ Reactive-JSON provides several built-in reactions:
 - **addData**: Adds new data to the specified path.
 - **removeData**: Removes data from the specified path.
 - **moveData**: Moves data from one path to another.
+- **toggleData**: Adds a value to an array when absent, removes it when present.
+- **collectField**: Writes the values of a field of every item of a collection as an array.
+- **joinData**: Writes a string built from several parts.
+- **stringifyData**: Writes the JSON representation of a value.
 
 ### Network Operations
 - **fetchData**: Fetches data from a URL using GET requests.
@@ -81,6 +85,7 @@ Reactive-JSON provides several built-in reactions:
 - **redirectNow**: Performs an immediate redirect.
 - **triggerEvent**: Triggers a custom event.
 - **postMessage**: Sends a message to another window/frame.
+- **printPage**: Opens the print dialog of the browser.
 
 For detailed documentation of each reaction, including properties and examples, see their respective documentation pages.
 

package/public/rjbuild/docs/getting-started/reactions.yaml

@@ -96,6 +96,10 @@ renderView:
       - **[addData](../core/reaction/addData)**: Adds new data to the specified path.
       - **[removeData](../core/reaction/removeData)**: Removes data from the specified path.
       - **[moveData](../core/reaction/moveData)**: Moves data from one path to another.
+      - **[toggleData](../core/reaction/toggleData)**: Adds a value to an array when absent, removes it when present.
+      - **[collectField](../core/reaction/collectField)**: Writes the values of a field of every item of a collection as an array.
+      - **[joinData](../core/reaction/joinData)**: Writes a string built from several parts.
+      - **[stringifyData](../core/reaction/stringifyData)**: Writes the JSON representation of a value.
 
       ### Network Operations
       - **[fetchData](../core/reaction/fetchData)**: Fetches data from a URL using GET requests.
@@ -106,6 +110,7 @@ renderView:
       - **[redirectNow](../core/reaction/redirectNow)**: Performs an immediate redirect.
       - **[triggerEvent](../core/reaction/triggerEvent)**: Triggers a custom event.
       - **[postMessage](../core/reaction/postMessage)**: Sends a message to another window/frame.
+      - **[printPage](../core/reaction/printPage)**: Opens the print dialog of the browser.
 
       For detailed documentation of each reaction, including properties and examples, see their respective documentation pages.
 

package/public/rjbuild/docs/getting-started/rjbuild-structure.md

@@ -355,7 +355,7 @@ additionalDataSource:
 
 #### Mixing all three types
 
-Path parts (plain strings, `~~.`/`~.` strings, and `segment` objects) are concatenated in order. All `param` objects are collected and appended as a query string after the path.
+Path parts (plain strings, `~~.`/`~.` strings, and `segment` objects) are concatenated in order. All `param` objects are collected and appended as a query string after the path. When the path already holds a query string (`/api/items?sort=asc`), the parameters continue it with `&`.
 
 ```yaml
 additionalDataSource:
@@ -400,6 +400,24 @@ data:
   timeLogs: []
 ```
 
+#### The same format elsewhere
+
+The segments format is also accepted by:
+
+- `url` of the [fetchData](../core/reaction/fetchData.md) and [submitData](../core/reaction/submitData.md) reactions: no request is sent when a required segment is empty;
+- `to` of the [redirectNow](../core/reaction/redirectNow.md) reaction: no navigation when a required segment is empty;
+- the URL attributes (`href`, `src`, `action`, `formAction`, `poster`) of any element: the attribute is omitted when a required segment is empty;
+- `parts` of the [joinData](../core/reaction/joinData.md) reaction, which writes the composed string in the data.
+
+There, the references are evaluated in the current template context: `~.slug` reads the current template data (e.g. the current `Switch` item), `~~.` the global data, `~>key` an ancestor. In `additionalDataSource.src`, both `~.` and `~~.` read the root data.
+
+```yaml
+- type: a
+  attributes:
+    href: ["/article/", ~.year, "/", { segment: ~.slug, required: true }]
+  content: ~.title
+```
+
 ### Fallback Sources
 
 The `fallbackDataSource` property defines an alternate source that is tried automatically when the primary source cannot be used. It accepts the same structure as a regular `additionalDataSource` item, including its own `fallbackDataSource` for chaining.

package/public/rjbuild/docs/getting-started/rjbuild-structure.yaml

@@ -379,7 +379,7 @@ renderView:
 
       #### Mixing all three types
 
-      Path parts (plain strings, `~~.`/`~.` strings, and `segment` objects) are concatenated in order. All `param` objects are collected and appended as a query string after the path.
+      Path parts (plain strings, `~~.`/`~.` strings, and `segment` objects) are concatenated in order. All `param` objects are collected and appended as a query string after the path. When the path already holds a query string (`/api/items?sort=asc`), the parameters continue it with `&`.
 
   - type: TabbedSerializer
     yamlSerializedContent: |
@@ -428,6 +428,26 @@ renderView:
         taskId: ""    # Will be overridden by dataOverride
         timeLogs: []
 
+  - type: Markdown
+    content: |
+      #### The same format elsewhere
+
+      The segments format is also accepted by:
+
+      - `url` of the [fetchData](../core/reaction/fetchData) and [submitData](../core/reaction/submitData) reactions: no request is sent when a required segment is empty;
+      - `to` of the [redirectNow](../core/reaction/redirectNow) reaction: no navigation when a required segment is empty;
+      - the URL attributes (`href`, `src`, `action`, `formAction`, `poster`) of any element: the attribute is omitted when a required segment is empty;
+      - `parts` of the [joinData](../core/reaction/joinData) reaction, which writes the composed string in the data.
+
+      There, the references are evaluated in the current template context: `~.slug` reads the current template data (e.g. the current `Switch` item), `~~.` the global data, `~>key` an ancestor. In `additionalDataSource.src`, both `~.` and `~~.` read the root data.
+
+      ```yaml
+      - type: a
+        attributes:
+          href: ["/article/", ~.year, "/", { segment: ~.slug, required: true }]
+        content: ~.title
+      ```
+
   - type: Markdown
     content: |