n8n-nodes-test-node 1.0.14 → 1.0.16
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/README.md +2 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -15,7 +15,7 @@ npm install n8n-nodes-test-node
|
|
|
15
15
|
## What was generated
|
|
16
16
|
|
|
17
17
|
- Node type(s) in this package: **remoteChromiumCDPAutomationAPI**, **remoteChromiumCDPAutomationAPITool** (AI Agent tool).
|
|
18
|
-
- 13 resource(s), 74 operation(s) (identical parameter set on
|
|
18
|
+
- 13 resource(s), 74 operation(s) (identical parameter set on the regular and tool nodes -- they share the same credential and routing, differing only in identity and how they present themselves).
|
|
19
19
|
- Credential type **remoteChromiumCDPAutomationAPIApi**, with an editable **Base URL** field, plus: API Key / Bearer token field(s) per the spec's security scheme.
|
|
20
20
|
- Default Base URL: `https://api.example.com/v1` (the spec declared no `servers[0].url`, so this is a placeholder -- edit the credential's "Base URL" field before using the node)
|
|
21
21
|
|
|
@@ -34,6 +34,7 @@ Once installed and enabled, add an **AI Agent** node to your workflow, and this
|
|
|
34
34
|
- OAuth2 and HTTP Basic each use n8n's own built-in credential mechanism and can't be combined with each other or with API Key/Bearer in one credential. If a spec declares more than one auth *family* as alternatives, this generator picks one deterministically -- **OAuth2 > HTTP Basic > API Key/Bearer** -- and the rest are ignored (logged during generation, and listed above if applicable). Multiple schemes *within* the API Key/Bearer family are still combined into one credential.
|
|
35
35
|
- If some operations require only an unsupported scheme while others are covered by this node's credential (the classic Swagger Petstore spec is a real example -- OAuth2 implicit flow for writes, an API key for some reads), the unsupported operations are left out of the node rather than the whole build failing -- see above for which ones, if any.
|
|
36
36
|
- Request bodies with nested objects, arrays, or genuine `oneOf`/`anyOf`/`allOf` type unions are exposed as a single raw "Body (JSON)" field rather than individual fields. A nullable/optional primitive field (OpenAPI 3.1's `anyOf: [{type: 'string'}, {type: 'null'}]`, as FastAPI/Pydantic generates for `Optional[str]`) is still recognized as simple and gets its own field.
|
|
37
|
+
- The Files node keeps every field top-level (no "Additional Fields" grouping for optional params, unlike the main node) -- binary operations tend to have few parameters, so this keeps its hand-written `execute()` logic simpler.
|
|
37
38
|
|
|
38
39
|
## Regenerating
|
|
39
40
|
|