Lucio Lelii
1abdb5b591
Starting a fresh run means retyping values you already typed. The panel now offers the other runs of this execution's own group - the group is keyed by source flow, so a run of a different flow is never offered: matching its inputs by name would be a coincidence, not a copy. The copy fills the panel's pending edits rather than writing anything. That is the whole trick: the values arrive with the unsaved-change styling already on them, the user reviews them, and the single Save sends them in one bulk request. No new write path, no new error handling. It is deliberately partial, and says so. A file input holds a temp file on the server, which the backend copies by reference when it reruns an execution; from here there is only a path, and copying it would point this run at another run's upload. Credentials are not copyable at all - the vault decrypts them server-side. Both are reported in the summary rather than dropped quietly, because a copy that silently leaves gaps is worse than one that names them. Worth knowing before reaching for this: a rerun, bias rerun included, already arrives fully populated - createBiasRerun calls copyReusableInputs, which carries over every node input, the global descriptors, the authorizations and the simulation descriptor. This is for the case that copies nothing: a new run created from the flow. An input already matching the source is not offered as a change, since it would join the unsaved count and invite a pointless save. 555 frontend tests green; initial bundle unchanged at 2.88 kB over budget. 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.