Lucio Lelii
46976b1f92
While verifying the dialog style convergence, found that generic-node's "Edit <field>" popup and container-node's "Edit Name" popup have the same bug just fixed in bias-annotations: they render inside the node card, which rete.js positions with a CSS transform for pan/zoom, so their fixed-position .llm-modal-backdrop was trapped inside the node's own box instead of covering the page — confirmed live, the backdrop's bounding rect matched the node's box (280x533) rather than the viewport. This popup is the primary way to edit any short parameter on any node in the editor, so the bug was hit far more often than the bias one. Same fix: promote the backdrop to a native <dialog> shown via showModal(), move the dimming to ::backdrop, and guard showModal() since jsdom doesn't implement it. Verified live: the backdrop's rect now spans the full viewport for both generic-node and container-node, and closing via a backdrop click still works. 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.