@ea-lab/reactive-json-docs 1.2.0 → 1.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -90,6 +90,30 @@ data:
90
90
  name: "Marie"
91
91
  ```
92
92
 
93
+ ### Arrays in Content vs. Attributes
94
+
95
+ - Arrays are supported in `content` to render multiple text nodes or elements in sequence (they are not string concatenations).
96
+ - Do not use arrays inside HTML attributes (e.g., `href`, `class`, `id`). Attributes expect a single value. If you need a composed value, compute it beforehand and pass the final string.
97
+
98
+ Example (valid):
99
+ ```yaml
100
+ content: ["Go to ", ~.sectionName]
101
+ ```
102
+
103
+ Example (invalid in attributes):
104
+ ```yaml
105
+ # ❌ Do not do this
106
+ attributes:
107
+ href: ["#", ~.id]
108
+ ```
109
+
110
+ Instead, prepare the value upstream:
111
+ ```yaml
112
+ # ✅ Provide a ready-to-use attribute value
113
+ attributes:
114
+ href: ~.href # where href is a string like "#section-3"
115
+ ```
116
+
93
117
  ## Section `data` (Optional)
94
118
 
95
119
  The `data` section contains the **initial state** of the application. This data can be read and modified by components.
@@ -104,6 +104,32 @@ renderView:
104
104
  user:
105
105
  name: "Marie"
106
106
 
107
+ - type: Markdown
108
+ content: |
109
+ ### Arrays in Content vs. Attributes
110
+
111
+ - Arrays are supported in `content` to render multiple text nodes or elements in sequence (they are not string concatenations).
112
+ - Do not use arrays inside HTML attributes (e.g., `href`, `class`, `id`). Attributes expect a single value. If you need a composed value, compute it beforehand and pass the final string.
113
+
114
+ Example (valid):
115
+ ```yaml
116
+ content: ["Go to ", ~.sectionName]
117
+ ```
118
+
119
+ Example (invalid in attributes):
120
+ ```yaml
121
+ # ❌ Do not do this
122
+ attributes:
123
+ href: ["#", ~.id]
124
+ ```
125
+
126
+ Instead, prepare the value upstream:
127
+ ```yaml
128
+ # ✅ Provide a ready-to-use attribute value
129
+ attributes:
130
+ href: ~.href # where href is a string like "#section-3"
131
+ ```
132
+
107
133
  - type: Markdown
108
134
  content: |
109
135