Lucio Lelii
8659b798d5
In the parent's execution graph a container's own status is WAITING_FOR_SUBFLOW, so it took none of the in-progress styling and sat there inert for minutes while its child ran. Combined with a tree that was not refreshing, a working run was indistinguishable from a stuck one. The card now pulses on the same rhythm as a running node, in indigo rather than yellow because the work is a level down: the node is not computing, it is waiting on a child, and that child is the thing worth opening. A badge names the iteration in flight - __containerIterationIndex is new on the graph payload - so the signal says what is happening and not merely that something is. An errored container does not pulse: there the error is what matters. Motion is now suppressed under prefers-reduced-motion, with the pulses settling on their emphasised frame so the state survives without the animation. That covers the two pre-existing pulses as well - adding a third blinking element is the point where honouring the setting stops being optional. Budgets: task-step-node.css went 122 bytes over, so the badge icon lost its spin (the border pulse already carries "in progress"). The initial bundle is still 2.21 kB over its 1.75 MB budget, up from being just inside it - reported, not raised. 497 frontend tests green; the new assertions fail with the class binding removed. 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.