Lucio Lelii
b2d744fe42
The Bias impact tab is empty because no experiment has ever run - zero rows in bias_impact_report_entity - and nothing in the UI said how one is started. The empty state now explains what a report is, says how many nodes carry a probe that can be activated on this run, and offers the action. When something is in the way it states that instead: a subflow cannot be a baseline, an unfinished run cannot be compared against a rerun, a flow with no activatable probe has nothing to measure. "Create biased rerun" no longer returns silently when no node qualifies - a button that does nothing and explains nothing is indistinguishable from a broken one. It now names the reason. The per-node measure control is shown on interactive blocks instead of hidden. ChatInteraction cannot be replayed in isolation, so the isolated experiment is genuinely unavailable there - but hiding the control made an annotated node look identical to an unannotated one. It is rendered disabled, and the tooltip points at the full-flow route that does work. That is a rule of the domain, worth stating rather than concealing. Splitting the node scan out of biasRerunCandidates keeps this free: the count is computed from the flow snapshot, while only the capability check needs the network. 506 frontend tests green; each new assertion fails when its behaviour is undone. Initial bundle now 2.86 kB over budget, up from 2.21 kB - reported, not raised. 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.