@revenexx/integrations-node-sdk 1.5.1 → 1.6.0
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/index.d.cts +21 -1
- package/dist/index.d.ts +21 -1
- package/package.json +1 -1
package/dist/index.d.cts
CHANGED
|
@@ -58,12 +58,18 @@ interface IInputPort {
|
|
|
58
58
|
* One value an output carries, as the editor offers it to the next step.
|
|
59
59
|
*
|
|
60
60
|
* Deliberately flat: there is no member describing what is inside the value,
|
|
61
|
-
* because the registry's manifest schema refuses any key beside these
|
|
61
|
+
* because the registry's manifest schema refuses any key beside these three and
|
|
62
62
|
* the studio reads none. What is inside a value is declared beside it, under a
|
|
63
63
|
* dotted name — see `IOutputPort.fields` (PO-408).
|
|
64
64
|
*/
|
|
65
65
|
interface IOutputField {
|
|
66
66
|
dataType: DataType;
|
|
67
|
+
/**
|
|
68
|
+
* What the value is called, for an author picking it in the editor's `{ }` list —
|
|
69
|
+
* "Rechnungen" where the key is `invoices` (PO-594). Left out, the editor shows the
|
|
70
|
+
* key, as before.
|
|
71
|
+
*/
|
|
72
|
+
label?: LocalizedString;
|
|
67
73
|
description?: LocalizedString;
|
|
68
74
|
}
|
|
69
75
|
interface IOutputPort {
|
|
@@ -171,6 +177,20 @@ interface IConfigFieldBase {
|
|
|
171
177
|
* know the key.
|
|
172
178
|
*/
|
|
173
179
|
showIf?: IShowIfCondition;
|
|
180
|
+
/**
|
|
181
|
+
* What a value mapped into this field from an earlier step has to be — `'array'`
|
|
182
|
+
* for a setting that wants the list a previous node produced (PO-594).
|
|
183
|
+
*
|
|
184
|
+
* The editor uses it to put the earlier steps' outputs of that kind first in the
|
|
185
|
+
* `{ }` list, mark them, and offer the single matching one as a one-click answer
|
|
186
|
+
* under an empty field. So the author does not have to know what a previous node
|
|
187
|
+
* returns, or which of its fields is the list.
|
|
188
|
+
*
|
|
189
|
+
* Not to be confused with `type: 'array'`, which draws the setting itself as
|
|
190
|
+
* repeating rows the author fills in by hand. Only meaningful together with
|
|
191
|
+
* `expressionAllowed`. Left unset, every output is offered alike, as before.
|
|
192
|
+
*/
|
|
193
|
+
accepts?: DataType;
|
|
174
194
|
/**
|
|
175
195
|
* Only meaningful when `type === 'credentials-ref'`: the namespaced slug(s) of
|
|
176
196
|
* the credential type(s) this field accepts (e.g. `revenexx:smtp`). The editor
|
package/dist/index.d.ts
CHANGED
|
@@ -58,12 +58,18 @@ interface IInputPort {
|
|
|
58
58
|
* One value an output carries, as the editor offers it to the next step.
|
|
59
59
|
*
|
|
60
60
|
* Deliberately flat: there is no member describing what is inside the value,
|
|
61
|
-
* because the registry's manifest schema refuses any key beside these
|
|
61
|
+
* because the registry's manifest schema refuses any key beside these three and
|
|
62
62
|
* the studio reads none. What is inside a value is declared beside it, under a
|
|
63
63
|
* dotted name — see `IOutputPort.fields` (PO-408).
|
|
64
64
|
*/
|
|
65
65
|
interface IOutputField {
|
|
66
66
|
dataType: DataType;
|
|
67
|
+
/**
|
|
68
|
+
* What the value is called, for an author picking it in the editor's `{ }` list —
|
|
69
|
+
* "Rechnungen" where the key is `invoices` (PO-594). Left out, the editor shows the
|
|
70
|
+
* key, as before.
|
|
71
|
+
*/
|
|
72
|
+
label?: LocalizedString;
|
|
67
73
|
description?: LocalizedString;
|
|
68
74
|
}
|
|
69
75
|
interface IOutputPort {
|
|
@@ -171,6 +177,20 @@ interface IConfigFieldBase {
|
|
|
171
177
|
* know the key.
|
|
172
178
|
*/
|
|
173
179
|
showIf?: IShowIfCondition;
|
|
180
|
+
/**
|
|
181
|
+
* What a value mapped into this field from an earlier step has to be — `'array'`
|
|
182
|
+
* for a setting that wants the list a previous node produced (PO-594).
|
|
183
|
+
*
|
|
184
|
+
* The editor uses it to put the earlier steps' outputs of that kind first in the
|
|
185
|
+
* `{ }` list, mark them, and offer the single matching one as a one-click answer
|
|
186
|
+
* under an empty field. So the author does not have to know what a previous node
|
|
187
|
+
* returns, or which of its fields is the list.
|
|
188
|
+
*
|
|
189
|
+
* Not to be confused with `type: 'array'`, which draws the setting itself as
|
|
190
|
+
* repeating rows the author fills in by hand. Only meaningful together with
|
|
191
|
+
* `expressionAllowed`. Left unset, every output is offered alike, as before.
|
|
192
|
+
*/
|
|
193
|
+
accepts?: DataType;
|
|
174
194
|
/**
|
|
175
195
|
* Only meaningful when `type === 'credentials-ref'`: the namespaced slug(s) of
|
|
176
196
|
* the credential type(s) this field accepts (e.g. `revenexx:smtp`). The editor
|