Add restricted middleware transformation pipelines

This commit is contained in:
2026-11-05 23:07:36 +00:00
parent 163f99be54
commit f7a06f487c
5 changed files with 88 additions and 11 deletions
+2 -1
View File
@@ -26,6 +26,7 @@ The initial landscape contains Website, API, ERP, CRM and Email Platform plus tw
- Place reusable Website, CRM, ERP, Email Platform, Analytics and API presets, selecting only the capabilities needed for each instance.
- Inspect labelled capability ports and fictional action payloads, expand node actions, and save customised systems as private browser-local presets.
- Build reusable custom systems with form-based action, output and endpoint definitions. Actions support button, incoming request/event and simulated schedule triggers; outputs can run in parallel, and endpoints support multiple delayed example responses that may trigger actions.
- Add restricted transformation pipelines to action definitions for middleware-style Receive, Validate, Transform, Route and Send stages. Pipelines support explicit example payloads, copy/rename/fixed/default/type-conversion/object-construction/array-item-mapping rules, reference lookup values, validation-failure paths and playback inspection without executing arbitrary JavaScript. The demo includes Website → Order Middleware → ERP.
- Model direct request/response exchanges separately from onward event transfers. Request and response payloads are both recorded in the data inspector, with compatibility warnings shown without blocking unusual integrations.
- Run, pause, advance and reset scenarios with animated packets and event log output.
- Adjust playback speed and inspect the active payload.
@@ -40,4 +41,4 @@ npm run build
## Limitations
This is intentionally a local simulation prototype. It has no authentication, collaboration, server persistence, external API calls, real payload delivery, or production-grade graph editing. Custom definitions and placed instances are stored in browser local storage; playback state is transient and is not included in saved JSON. LiteGraph supplies canvas rendering and cable interaction; scenario semantics are managed by the Vue application. The minimap is diagnostic rather than a full viewport navigator, and transformation highlighting currently compares top-level JSON fields.
This is intentionally a local simulation prototype. It has no authentication, collaboration, server persistence, external API calls, real payload delivery, or production-grade graph editing. Custom definitions and placed instances are stored in browser local storage; playback state is transient and is not included in saved JSON. LiteGraph supplies canvas rendering and cable interaction; scenario semantics are managed by the Vue application. The minimap is diagnostic rather than a full viewport navigator, and transformation highlighting currently compares top-level JSON fields. Pipeline mappings are deliberately limited to the listed rule operations; arbitrary JavaScript, network lookups and live middleware execution are not supported. The custom builder exposes pipeline definitions as validated JSON so advanced step graphs can be edited without adding another runtime dependency.