Lucio Lelii
984af08f36
The report carried a single `judge`, so asking a second model overwrote the first - there was no way to compare two opinions, and reopening a report after a re-evaluation only ever showed the newest one. The viewer now renders `judgements`, newest first, each collapsible: the current one open and labelled so, the earlier ones a click away with their own verdicts, narrative and errors. A report saved with the old single field still reads, as a history of one. Also: closing the dialog while an assessment was running left `judging` stuck true forever, so reopening any report showed a disabled button stuck on "Evaluating...". And opening a different report while one was still running let the late answer land on it, silently replacing the report on screen with someone else's assessment. Both dialogs now carry a token that advances whenever what they're showing changes; a response that arrives after its token is stale gets discarded instead of applied. The job itself is unaffected - it keeps running server-side and its verdicts land on the report regardless, which is what makes reopening it later still show them. Co-Authored-By: Claude Sonnet 5 <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.