Written here rather than pulled in: there is no diff library in the project, the initial bundle is already over budget, and what is needed is small. Side by side without it, two paragraphs of model output differing in one clause have to be read twice to find the clause. Word-level, not character-level: the values are prose, and a character diff on a rewritten sentence produces confetti rather than an explanation. Each word carries its trailing whitespace. As separate tokens the spaces match between any two texts, so a wholly rewritten sentence came back as alternating removed-word / kept-space parts - the same confetti, arrived at from the other direction. A test caught this; the tokenizer changed, not the expectation. The LCS table is quadratic in tokens, and two long model outputs are exactly what this exists for, so past a guard it falls back to whole-value replacement rather than freezing the view it is meant to render. 525 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.