@devkong/cli-nx 0.0.55 → 0.0.56
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/package.json
CHANGED
|
@@ -43,6 +43,31 @@ To automatically tag your code with an incremented version number (e.g., 1, 2, 3
|
|
|
43
43
|
kong publish-version --verbose
|
|
44
44
|
```
|
|
45
45
|
|
|
46
|
+
**NOTE:** before publishing a new version, ensure that your extension JSON Schema includes the required `operation` field. This input field has `enum` type and defines the action to be performed by the extension.
|
|
47
|
+
|
|
48
|
+
**Purpose:**
|
|
49
|
+
|
|
50
|
+
- When an extension supports multiple usage variants or endpoints, this field identifies the specific operation to execute.
|
|
51
|
+
- It enables routing and logic selection within the extension workflow.
|
|
52
|
+
- If an extension has only one primary function, this `enum` contains a single value that uniquely identifies its operation.
|
|
53
|
+
|
|
54
|
+
**Usage Example:**
|
|
55
|
+
|
|
56
|
+
```
|
|
57
|
+
"$schema": "http://json-schema.org/draft-07/schema#",
|
|
58
|
+
"title": "Input",
|
|
59
|
+
"type": "object",
|
|
60
|
+
"properties": {
|
|
61
|
+
"operation": {
|
|
62
|
+
"enum": ["score digital profile", ...],
|
|
63
|
+
"examples": ["score digital profile"],
|
|
64
|
+
"description": "Operation type."
|
|
65
|
+
},
|
|
66
|
+
...
|
|
67
|
+
"required": ["operation", ... ]
|
|
68
|
+
}
|
|
69
|
+
```
|
|
70
|
+
|
|
46
71
|
### List Available Versions
|
|
47
72
|
|
|
48
73
|
To see all available versions of your extension, run:
|
|
@@ -46,6 +46,31 @@ To automatically tag your code with an incremented version number (e.g., 1, 2, 3
|
|
|
46
46
|
kong publish-version --verbose
|
|
47
47
|
```
|
|
48
48
|
|
|
49
|
+
**NOTE:** before publishing a new version, ensure that your extension JSON Schema includes the required `operation` field. This input field has `enum` type and defines the action to be performed by the extension.
|
|
50
|
+
|
|
51
|
+
**Purpose:**
|
|
52
|
+
|
|
53
|
+
- When an extension supports multiple usage variants or endpoints, this field identifies the specific operation to execute.
|
|
54
|
+
- It enables routing and logic selection within the extension workflow.
|
|
55
|
+
- If an extension has only one primary function, this `enum` contains a single value that uniquely identifies its operation.
|
|
56
|
+
|
|
57
|
+
**Usage Example:**
|
|
58
|
+
|
|
59
|
+
```
|
|
60
|
+
"$schema": "http://json-schema.org/draft-07/schema#",
|
|
61
|
+
"title": "Input",
|
|
62
|
+
"type": "object",
|
|
63
|
+
"properties": {
|
|
64
|
+
"operation": {
|
|
65
|
+
"enum": ["score digital profile", ...],
|
|
66
|
+
"examples": ["score digital profile"],
|
|
67
|
+
"description": "Operation type."
|
|
68
|
+
},
|
|
69
|
+
...
|
|
70
|
+
"required": ["operation", ... ]
|
|
71
|
+
}
|
|
72
|
+
```
|
|
73
|
+
|
|
49
74
|
### List Available Versions
|
|
50
75
|
|
|
51
76
|
To see all available versions of your extension, run:
|