A storage node comes from the server with the RESOURCE role. In the editor it is drawn apart from the steps - dashed, teal, labelled 'Storage · not a step' - and its targets take a connection from every step that writes there; a view parameter (<view>.<parameter>) still takes one. Its edges are left out when the editor works out which connections lead back round a loop: a write followed by a read of the same node is not a cycle, the same view the server takes. The execution view draws the node from the flow, since it never has a step, with no status of its own, so the reads and writes on its edges still have somewhere to go. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| app | ||
| environments | ||
| index.html | ||
| main.ts | ||
| runtime-config.d.ts | ||
| styles.css | ||