@celigo/api-specs 0.2.81 → 0.2.83
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 +135 -740
- package/dist/import.yml +9 -0
- package/dist/tool.yml +144 -740
- package/package.json +1 -1
- package/schemas.json +2 -2
package/dist/import.yml
CHANGED
|
@@ -1943,6 +1943,15 @@ components:
|
|
|
1943
1943
|
(verified 2026-09-21 on create, on PUT, and after a re-save). Keep
|
|
1944
1944
|
each entry equal to the endpoint you mean so the pointer and the
|
|
1945
1945
|
request agree. Get the URI shape right.
|
|
1946
|
+
- |-
|
|
1947
|
+
On a GraphQL-form import (`formType` `graph_ql` / `assistant_graphql`) the form owns
|
|
1948
|
+
this field: it shows no relative-URI field and writes `["/"]` back on every save in the
|
|
1949
|
+
editor, because the request path is expected to come from the connection's `baseURI` —
|
|
1950
|
+
a `graph_ql` connection, or a connector connection bound to its GraphQL API. A path set
|
|
1951
|
+
here through the API on such an import does reach the wire, but it is invisible in the
|
|
1952
|
+
editor and reverts to `["/"]` the next time the import is saved there; when the
|
|
1953
|
+
connection's base URI stops at an API root, move the import to a connection that
|
|
1954
|
+
supplies the GraphQL endpoint instead of patching this field.
|
|
1946
1955
|
examples:
|
|
1947
1956
|
- - /api/v1/customers
|
|
1948
1957
|
- - /customers/{{{data.0.shopifyCustomerId}}}.json
|