Lucio Lelii
c7cefaca96
An execution cannot start until every requiredAuthorizations entry is satisfied. A key of the form LLMProvider::<provider>::authorization is answered with a vault secret id chosen from a picker filtered by that provider, or from a credential created on the spot; anything else keeps the literal-value panel it had. A provider key never falls through to the literal-value panel, whatever the provider catalog says or fails to say, so the API key itself can no longer be pasted as the authorization value. The catalog is therefore no longer part of the gate: an outstanding requirement blocks the start on its own, and a failed catalog read is a notice with a retry. The authorizations PUT answers with the recomputed execution, so its response replaces the execution in the store rather than triggering a list refresh, and the backend's 400 message reaches the user. A settled requirement stays on screen with the credential label and a change action, and a banner above the graph names the missing providers when the context aside is collapsed. The gate itself is now pure - buildAuthorizationGate and isExecutionStartable in execution-viewer.utils.ts - and covered by tests, since the component cannot be instantiated under the test environment. 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.