Lucio Lelii
bf4ed026b2
A green play and a flask said nothing about the one thing that separates them: whether you answer the flow's chat and decision steps, or an LLM answers them for you. The flask was actively misleading - "experiment" is the bias experiments' word, so it pointed at a different feature. Both buttons now keep the play, and a small badge carries the difference: a person, or a robot. A gear was the first thought and is the wrong glyph - it is the settings icon everywhere else in the product, so on a run button it reads as "configure this run" rather than "a machine runs it". They also sit next to each other now. Stop and resume used to separate them, so each had to be understood alone - which is precisely the job a 17px badge cannot do. Side by side they are one choice, and each is what makes the other legible. The tooltips stop repeating the button and say who answers: "Run - you answer the human steps", "Run simulated - an LLM answers the human steps". That is the sentence the icon can only gesture at. 557 frontend tests green. 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.