lelii
/
humainflow-web
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
170 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 53ac229790 Refresh the Bias impact tab when a report is produced 
The list fetched only when executionId changed. The experiment and compare
dialogs are global hosts rendered over the still-mounted aside, so the sequence
that actually happens - open the tab, run an experiment, read the report in the
dialog, close it - returned the user to a tab still claiming there were no
reports. There was no refresh either: retry() is rendered only in the error
branch.

A small shared signal announces that a report now exists. The dialogs raise it
rather than the viewer, because they are what knows one was actually produced -
a failed experiment produces none - and it keeps the viewer out of a path it has
no part in.

A reload of the same execution keeps an open report open; only a change of
execution closes it, since that is a different subject.

500 frontend tests green. The reload assertion fails when the revision is
ignored again.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
 		2026-09-03 17:35:23 +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 Refresh the Bias impact tab when a report is produced 2026-09-03 17:35:23 +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.