The picker for a simulator or a judge and a node's parameter panel are the same dialog component, and the dialog has always known how to offer "Use default" on an optional field - showUseDefault, the "Using the default" hint, the reset. It reads one flag, defaultsWhenEmpty, which the node panels set on every optional field and this hand-written list never set at all. So a temperature typed here by mistake had no way back to unset: clearing the box by hand looks the same as never having decided. Set it on all five, and brought the rest of each field in line with what the schema-driven panel produces for the same object: an arrow step a decimal can actually move by, an integer step on the integers, and the tips ModelParameters itself declares, so the same explanation appears in both places. Temperature's max was 2 here and is 1.0 on the server, which has a comment explaining why - the dialog was offering a value the run would be rejected for. Still hand-written rather than derived from the published schema: this dialog picks a model for a run, not a node's configuration, and reaching for a block type's schema to render five known fields would buy a network call and a way to fail. 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.