Lucio Lelii
fcb8c0957a
The dialog/modal CSS across the app hardcodes the same handful of values (border-radius, box-shadow, surface/border/muted-text colors, z-index) independently in each component, with several components already drifting to slightly different values for the same intent. Add a small set of :root custom properties in styles.css (radius, shadow, surface/border/text colors, spacing scale, modal z-index ladder) and migrate modal-shell.css — the shared shell already used by three dialogs — onto them first, as the lowest-risk starting point. Values are unchanged, only their source moved to tokens, so this is a no-op visually: verified via the existing test suite (232/232) and a live browser check confirming computed values are unchanged and the editor/dashboard render identically. Follow-up: retrofit confirm-dialog, node-settings-dialog, human-interaction-dialog and subflow-preview-dialog onto the same tokens, then reconcile node CSS (generic-node/container-node). 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.