lelii
/
humainflow-web
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
169 Commits 1 Branch 0 Tags 7.3 MiB
TypeScript 77.2%
HTML 13.1%
CSS 9.3%
Python 0.4%
Go to file
Lucio Lelii c35bbc0ccf Compare the bias mode against the value the API actually sends 
The backend enum is NORMAL | EXPERIMENT. isBiasVariantContext compared against
'BIAS_VARIANT', a value no endpoint has ever emitted, so it was always false and
took a whole feature path down with it:

- "Compare with baseline" is wrapped in @if (isBiasVariant()), so it never
  rendered - the only route to a FULL_FLOW bias report;
- the run list never labelled a rerun as a bias variant, which is the very thing
  it was changed to do;
- biasInterventionMix always returned null, so BIAS / MITIGATION / MIXED never
  showed.

I introduced this while fixing a real bug - presence of biasExecutionContext was
marking every run a variant - by correcting the condition to the wrong literal.
The fixtures used the same invented value, so the tests passed and the change
looked verified. They are corrected here too: with the old literal restored,
eight assertions now fail.

The two names are kept apart deliberately and both are commented: 'BIAS_VARIANT'
remains the list's own TaskExecutionKind vocabulary, while the API mode is
'EXPERIMENT'. Treating them as interchangeable is what caused this.

The dev fake was also seeding 'BIAS_VARIANT', so development agreed with the bug
and disagreed with the service.

497 frontend tests green.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
 		2026-09-03 17:32:38 +02:00
.vscode refactor: code quality improvements (tasks 1-15) 2026-04-09 14:53:02 +02:00
docker refactor: code quality improvements (tasks 1-15) 2026-04-09 14:53:02 +02:00
docs feat: improve auth flow and task execution UX 2026-04-09 14:01:56 +02:00
public solved node input output issue 2026-01-28 17:19:57 +01:00
src Compare the bias mode against the value the API actually sends 2026-09-03 17:32:38 +02:00
.dockerignore Add suspended execution resume support and production Docker setup 2026-03-22 10:35:30 +01:00
.editorconfig initial commit 2025-12-11 12:51:55 +01:00
.gitignore initial commit 2025-12-11 12:51:55 +01:00
.postcssrc.json initial commit 2025-12-11 12:51:55 +01:00
Dockerfile turnstile siteKey added with a env var 2026-03-26 13:51:31 +01:00
README.md Improve schema-driven nodes and interactive execution chat 2026-03-19 15:18:09 +01:00
angular.json Add suspended execution resume support and production Docker setup 2026-03-22 10:35:30 +01:00
components.json first commit 2026-01-07 16:07:33 +01:00
nginx.conf Add suspended execution resume support and production Docker setup 2026-03-22 10:35:30 +01:00
package-lock.json refactor: code quality improvements (tasks 1-15) 2026-04-09 14:53:02 +02:00
package.json refactor: code quality improvements (tasks 1-15) 2026-04-09 14:53:02 +02:00
tsconfig.app.json modified for deprecation 2026-04-10 09:08:38 +02:00
tsconfig.json modified for deprecation 2026-04-10 09:08:38 +02:00
tsconfig.spec.json modified for deprecation 2026-04-10 09:08:38 +02:00

README.md

HumAInFlow

This project was generated using Angular CLI version 21.0.3.

Development server

To start a local development server, run:

ng serve

Once 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-name

For a complete list of available schematics (such as components, directives, or pipes), run:

ng generate --help

Building

To build the project run:

ng build

This 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 test

Running end-to-end tests

For end-to-end (e2e) testing, run:

ng e2e

Angular 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.