Lucio Lelii
03ac4901ed
The picker (node-settings-dialog) shared --z-modal with every other dialog guest, so opening it from "Evaluate impact with LLM" - itself a modal - tied on z-index with the report behind it and lost on DOM order: it rendered, and its backdrop even blocked clicks, but neither was visible. It read as a button that did nothing. Named the layer this actually is - --z-dialog-over-modal, the same one the confirmation dialog already needed and had defined ad hoc as --z-confirm - and moved the picker onto it. While chasing this, closed a real silence next to it: with no LLM provider published at all, the picker answered null and the caller treated that like a dismissal, so the button did nothing for a second, unrelated reason. It now throws with a message, and Simulate surfaces it as a notification instead of swallowing it. 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.