mirror of
https://github.com/n8n-io/n8n.git
synced 2026-10-19 16:55:02 +02:00
33ad2d3680
Two cases where the answer needs the node composition of a set of workflows, not their names or their graphs. - `finds-the-real-users-of-a-node-type`: inside one folder, three workflows use the Postgres node and none says so in its name, while two more carry Postgres in the NAME and never use it. A name filter returns exactly the wrong two. - `reads-a-folders-node-conventions-before-extending-it`: what a folder is built out of, before adding to it. Two workflows outside the folder use nodes that appear nowhere inside it, so an instance-wide summary gives the wrong convention. Both are folder-scoped rather than instance-wide, for a reason worth recording: the eval instance is shared and already holds unrelated workflows, so an instance-wide count is not a fact a case can assert. Scoping also makes them test the two capabilities composed — the folder bounds the set, the index says which members actually contain the node. The out-of-folder pair in the second case deliberately avoids Postgres: cases share one project and run concurrently, so one case's seeds can otherwise answer another case's question. |
||
|---|---|---|
| .. | ||
| @n8n | ||
| cli | ||
| core | ||
| extensions/insights | ||
| frontend | ||
| modules | ||
| node-dev | ||
| nodes-base | ||
| testing | ||
| workflow | ||