Lucio Lelii
0dcdc6d135
A flow result is built only from *unconnected* outputs, so wiring the last block into an End node moves its value out of the result and into the outcome payload - which nothing in the UI read. The run then looked like it produced nothing at all. There is already an execution in a local database whose outcome payload is a full generated rejection email that was invisible for exactly this reason. The run view now has an Outcomes section above the graph, listing each End the run passed through: its code, its label, the step it came from, and its payload. An End reached with no value says so, rather than showing an empty box - the two cases mean different things. A text payload renders as text rather than through the JSON tree. The tree would have kept the line breaks but wraps strings in quotes, and the common case here is a generated document, not a data structure. This is the smallest of the options for the underlying gap: the data was already persisted and already in the API payload, so nothing in the engine changed. The gap itself remains - End cannot be attached as a pure ordering dependency (canDependOnOtherNodes is false), so a single-exit flow still has to choose between a labelled end and a value in `result`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .vscode | ||
| docker | ||
| docs | ||
| public | ||
| src | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| .postcssrc.json | ||
| Dockerfile | ||
| README.md | ||
| angular.json | ||
| components.json | ||
| nginx.conf | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.spec.json | ||
README.md
HumAInFlow
This project was generated using Angular CLI version 21.0.3.
Development server
To start a local development server, run:
ng serveOnce the server is running, open your browser and navigate to
http://localhost:4200/. The application will automatically
reload whenever you modify any of the source files.
Code scaffolding
Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
ng generate component component-nameFor a complete list of available schematics (such as
components, directives, or
pipes), run:
ng generate --helpBuilding
To build the project run:
ng buildThis will compile your project and store the build artifacts in the
dist/ directory. By default, the production build optimizes
your application for performance and speed.
Running unit tests
To execute unit tests with the Vitest test runner, use the following command:
ng testRunning end-to-end tests
For end-to-end (e2e) testing, run:
ng e2eAngular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
Additional Resources
For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.