Lucio Lelii
360ed5bd82
The second half: picking the pair, and showing the join. Selection is a mode of one group, and its own state. It is deliberately not folded into selectedExecutionId - that drives which run the main panel shows, so ticking a box would navigate away from what the user is reading. Confining it to a group is not tidiness either: runs of different flows share no step ids, so the join would report every node as replaced. A third pick replaces the older one rather than refusing the click, which would leave the user hunting for which box to clear. The view puts the two values side by side with the changed words marked, shows only the differing nodes by default, and compares outcomes alongside nodes - which is where the answer lives on a flow ending in an End node. An identical value is not diffed at all: running the table over text known to be the same can only output "all the same". Two things it says out loud rather than leaving to be inferred: that model output varies between runs on its own, so a difference is not by itself evidence of changed behaviour; and that two runs sharing no node are almost certainly runs of different versions of the flow, rather than a flow that changed entirely. 540 frontend tests green. The initial bundle grew 0.02 kB - the view lands in the lazy tasks-executor chunk - leaving it 2.88 kB over its budget. 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.