generator-agent 1.0.24 → 1.0.25

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.
@@ -43,12 +43,18 @@ Responsible for building generators that follow strict rules and guidelines base
43
43
 
44
44
  10. When params are used in a dynamic generator, the parameter names should be the same as those defined in the OpenAPI specification.
45
45
 
46
- 11. If you use param input from body, query, path or header, please make sure the reference path is correct and the field exists in the OpenAPI specification. For example: "$.input.body:$.ticketId" for request body, "$.input.query:$.status" for query parameter, "$.input.path:$.agentId" for path parameter, "$.input.header:$.Authorization" for header.
46
+ 11. If you use param input from body, query, path, or header, make sure the input path is correct and the field exists in the OpenAPI specification. For example: "$.input.body:$.ticketId" for request body, "$.input.query:$.status" for query parameter, "$.input.path:$.agentId" for path parameter, "$.input.header:$.Authorization" for header.
47
47
 
48
48
  12. If the same API with the same payload is needed more than once, call that API only once, store the entire response object, and extract all required values from that stored response.
49
49
 
50
50
  13. When storing an entire object in a generator, the `dataPath` must use the `:$` format (for example: `$.response.body:$`).
51
51
 
52
+ 14. Do not hardcode business values (for example department names/ids, status values, or entity identifiers) when they can be provided at runtime. Prefer parameterized input references (for example `$.input.query`, `$.input.body`, `$.input.path`, `$.input.header`) and pass them through generator params.
53
+
54
+ 15. When a runtime value is expected directly in `params`, provide it as an explicit placeholder string in this format: `"<provide_param_name>"` (for example: `"searchStr": "<provide_department_name>"`). Do not hardcode concrete business values.
55
+
56
+ 15. The first generator in any generator list must not be of type `reference`. Start with a data-producing generator type (for example `dynamic`, `static`, `remote`, or `conditional`) and use `reference` only after an earlier step has produced source data.
57
+
52
58
  ---
53
59
 
54
60
  ## Generator Structure Rule
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "name": "generator-agent",
3
3
  "displayName": "GeneratorAgent",
4
4
  "description": "Custom agent that responds with greetings and follows specific instructions",
5
- "version": "1.0.24",
5
+ "version": "1.0.25",
6
6
  "publisher": "Ishwarya",
7
7
  "author": "Ishwarya",
8
8
  "license": "MIT",