@lotics/app-sdk 0.83.0 → 0.83.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.
- package/docs/queries.md +6 -0
- package/package.json +1 -1
package/docs/queries.md
CHANGED
|
@@ -376,6 +376,12 @@ A `QuerySource` appears in `project.columns[].source`, `unpivot.passthrough[].so
|
|
|
376
376
|
| `{ "link": { "source": "customer", "field": "Company name" } }` | A field on the **first** linked record of a `select_record_link` field (correlated per-row subquery) | the target field's type |
|
|
377
377
|
| `{ "expression": "…" }` | jexpr escape hatch (below) | declared |
|
|
378
378
|
|
|
379
|
+
**Every variant in that table except the bare field key and `record_id` needs an explicit
|
|
380
|
+
`"type"` beside `"source"`, whatever the Output type column says it yields.** That column
|
|
381
|
+
describes the VALUE; the compiler infers a type only for a passthrough and for identity, and
|
|
382
|
+
rejects the column otherwise — so `{ "isNotEmpty": … }` is a boolean you still have to declare
|
|
383
|
+
as one. `record_id` is the sole exception, and declaring anything but `text` on it is rejected.
|
|
384
|
+
|
|
379
385
|
### Link extraction — the fine print
|
|
380
386
|
|
|
381
387
|
`{ link: { source, field } }` requires a direct `from_table` parent, and `source` must be a
|