@celigo/api-specs 0.2.46 → 0.2.47
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/dist/export.yml +24 -10
- package/dist/processor.yml +8 -3
- package/dist/tool.yml +24 -10
- package/package.json +1 -1
- package/schemas.json +2 -2
package/dist/export.yml
CHANGED
|
@@ -12683,6 +12683,13 @@ components:
|
|
|
12683
12683
|
There are two main parsing strategies available:
|
|
12684
12684
|
- **Automatic parsing**: Simple but produces more complex output
|
|
12685
12685
|
- **Custom parsing**: More control over the resulting JSON structure
|
|
12686
|
+
x-celigo-ai-guidance:
|
|
12687
|
+
- |-
|
|
12688
|
+
With V0_json false, an empty element (`<FirstName></FirstName>`, `<FirstName/>`) parses to
|
|
12689
|
+
an empty object `{}` under every setting here, not an empty string. A Handlebars template
|
|
12690
|
+
that outputs the field renders `[object Object]`; guard it with
|
|
12691
|
+
`{{#if (eq (typeOf FirstName) "string")}}{{FirstName}}{{/if}}` — a bare `{{#if FirstName}}`
|
|
12692
|
+
does not skip it because `{}` is truthy.
|
|
12686
12693
|
properties:
|
|
12687
12694
|
V0_json:
|
|
12688
12695
|
type: boolean
|
|
@@ -12704,22 +12711,29 @@ components:
|
|
|
12704
12711
|
listNodes:
|
|
12705
12712
|
type: array
|
|
12706
12713
|
description: |
|
|
12707
|
-
|
|
12708
|
-
|
|
12709
|
-
|
|
12710
|
-
|
|
12711
|
-
|
|
12712
|
-
|
|
12713
|
-
Each entry should be a simplified XPath expression pointing to the node that should be
|
|
12714
|
-
treated as an array.
|
|
12715
|
-
|
|
12716
|
-
Only relevant when V0_json is set to false (Custom parsing).
|
|
12714
|
+
Paths of elements that always parse as arrays. An element that can repeat parses as an
|
|
12715
|
+
object when it occurs once and as an array when it occurs more than once, so list every
|
|
12716
|
+
repeating element here to give each record the same shape regardless of item count.
|
|
12717
|
+
Each entry is the element's full path from the record element selected by the resource
|
|
12718
|
+
path (from the document root when there is no resource path), with an optional leading
|
|
12719
|
+
slash. Only relevant when V0_json is set to false (Custom parsing).
|
|
12717
12720
|
items:
|
|
12718
12721
|
type: string
|
|
12719
12722
|
examples:
|
|
12720
12723
|
- - /product-lineitems/product-lineitem
|
|
12721
12724
|
- /shipping-lineitems/shipping-lineitem
|
|
12722
12725
|
- /shipments/shipment
|
|
12726
|
+
x-celigo-ai-guidance:
|
|
12727
|
+
- |-
|
|
12728
|
+
Add every element that can repeat. Left out, a one-item record parses it as an object:
|
|
12729
|
+
a Handlebars `{{#each}}` over it iterates the object's fields (each field reference
|
|
12730
|
+
renders empty) and mappings or filters written against an array find nothing.
|
|
12731
|
+
- |-
|
|
12732
|
+
Write the full path from the record element: `Items/LineItemInfo` for records at
|
|
12733
|
+
resource path `/Orders/Order`. A bare descendant name (`LineItemInfo`) or a
|
|
12734
|
+
document-rooted path (`/Orders/Order/Items/LineItemInfo`) matches nothing while a
|
|
12735
|
+
resource path is set; without a resource path the path must start at the document
|
|
12736
|
+
root. `//Element` descendant paths never match.
|
|
12723
12737
|
includeNodes:
|
|
12724
12738
|
type: array
|
|
12725
12739
|
description: |
|
package/dist/processor.yml
CHANGED
|
@@ -195,9 +195,14 @@ paths:
|
|
|
195
195
|
items:
|
|
196
196
|
type: string
|
|
197
197
|
description: |-
|
|
198
|
-
|
|
199
|
-
|
|
200
|
-
|
|
198
|
+
Paths of elements that always parse as arrays. An
|
|
199
|
+
element that occurs once otherwise parses as an
|
|
200
|
+
object, and as an array only when it repeats. Each
|
|
201
|
+
entry is the element's full path from the record
|
|
202
|
+
element selected by `resourcePath` (from the
|
|
203
|
+
document root when `resourcePath` is unset), with
|
|
204
|
+
an optional leading slash; `//` descendant paths do
|
|
205
|
+
not match. Only active when `V0_json` is `false`.
|
|
201
206
|
includeNodes:
|
|
202
207
|
type: array
|
|
203
208
|
items:
|
package/dist/tool.yml
CHANGED
|
@@ -35639,6 +35639,13 @@ components:
|
|
|
35639
35639
|
There are two main parsing strategies available:
|
|
35640
35640
|
- **Automatic parsing**: Simple but produces more complex output
|
|
35641
35641
|
- **Custom parsing**: More control over the resulting JSON structure
|
|
35642
|
+
x-celigo-ai-guidance:
|
|
35643
|
+
- |-
|
|
35644
|
+
With V0_json false, an empty element (`<FirstName></FirstName>`, `<FirstName/>`) parses to
|
|
35645
|
+
an empty object `{}` under every setting here, not an empty string. A Handlebars template
|
|
35646
|
+
that outputs the field renders `[object Object]`; guard it with
|
|
35647
|
+
`{{#if (eq (typeOf FirstName) "string")}}{{FirstName}}{{/if}}` — a bare `{{#if FirstName}}`
|
|
35648
|
+
does not skip it because `{}` is truthy.
|
|
35642
35649
|
properties:
|
|
35643
35650
|
V0_json:
|
|
35644
35651
|
type: boolean
|
|
@@ -35660,22 +35667,29 @@ components:
|
|
|
35660
35667
|
listNodes:
|
|
35661
35668
|
type: array
|
|
35662
35669
|
description: |
|
|
35663
|
-
|
|
35664
|
-
|
|
35665
|
-
|
|
35666
|
-
|
|
35667
|
-
|
|
35668
|
-
|
|
35669
|
-
Each entry should be a simplified XPath expression pointing to the node that should be
|
|
35670
|
-
treated as an array.
|
|
35671
|
-
|
|
35672
|
-
Only relevant when V0_json is set to false (Custom parsing).
|
|
35670
|
+
Paths of elements that always parse as arrays. An element that can repeat parses as an
|
|
35671
|
+
object when it occurs once and as an array when it occurs more than once, so list every
|
|
35672
|
+
repeating element here to give each record the same shape regardless of item count.
|
|
35673
|
+
Each entry is the element's full path from the record element selected by the resource
|
|
35674
|
+
path (from the document root when there is no resource path), with an optional leading
|
|
35675
|
+
slash. Only relevant when V0_json is set to false (Custom parsing).
|
|
35673
35676
|
items:
|
|
35674
35677
|
type: string
|
|
35675
35678
|
examples:
|
|
35676
35679
|
- - /product-lineitems/product-lineitem
|
|
35677
35680
|
- /shipping-lineitems/shipping-lineitem
|
|
35678
35681
|
- /shipments/shipment
|
|
35682
|
+
x-celigo-ai-guidance:
|
|
35683
|
+
- |-
|
|
35684
|
+
Add every element that can repeat. Left out, a one-item record parses it as an object:
|
|
35685
|
+
a Handlebars `{{#each}}` over it iterates the object's fields (each field reference
|
|
35686
|
+
renders empty) and mappings or filters written against an array find nothing.
|
|
35687
|
+
- |-
|
|
35688
|
+
Write the full path from the record element: `Items/LineItemInfo` for records at
|
|
35689
|
+
resource path `/Orders/Order`. A bare descendant name (`LineItemInfo`) or a
|
|
35690
|
+
document-rooted path (`/Orders/Order/Items/LineItemInfo`) matches nothing while a
|
|
35691
|
+
resource path is set; without a resource path the path must start at the document
|
|
35692
|
+
root. `//Element` descendant paths never match.
|
|
35679
35693
|
includeNodes:
|
|
35680
35694
|
type: array
|
|
35681
35695
|
description: |
|
package/package.json
CHANGED