Lucio Lelii
dcf3af5551
Each input opened with a centred gradient badge whose largest text read "Flow" - the same word on every global input, so the most visual weight carried the least information - followed by a "Type:" line and a four-row textarea. A one-word positionTitle got the same box as a CV, and three short answers filled the panel. An input is now one line of chrome - name, a small type chip, and a dot saying whether it is still required - over a field that starts small. Removing an item from a list is an icon rather than a full-width "Remove" button, which at this width used to push the field out of the panel. Saving is one action for the panel. Per-input buttons meant a click and a round trip each, with nothing to say how much was still unsaved; a sticky bar now reports the pending count and saves them together. Each one still goes through the same single-input request, so a failure is still reported against its own input. The panel also stops ignoring missingGlobalInputKeys, which the backend has been sending all along: it now shows "2 of 5 provided" and marks exactly the inputs that block the start. The editor is one template instead of four near-identical copies - global and node, each single and multiple. That was not the goal here, but writing the same change four times is how those four drifted apart in the first place. First tests for this component. 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.