Lucio Lelii
8f8d2cb9f7
Making Gemini's model list empty left the assistant's own picker with an empty select and no way out: it has its own provider and model controls, not the schema-driven field machinery, so the rule that an unlistable catalogue has to be typed never reached it. Worse, it called the empty list "No models are available for the selected provider" - wrong twice, since the models exist and the message hid the fix. It now asks the same /open endpoint, and the four model controls - the main one and the three per-phase overrides, which were disabled outright while the list was empty - take a typed name. The question is asked alongside the list rather than derived from it: an open provider is exactly the one whose list comes back empty, so "nothing to show" and "nothing to offer" must not collapse into one answer. Closed on failure, which leaves a select the user can see is broken. The URL derivation moved to a shared helper. Both callers suffix the path while keeping the query string, and the provider rides in that query - a second copy of that detail is where the two would have drifted apart. 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.