Anchored to the bottom-left corner instead of the top-left: the top is where the run's own title and toolbar are, so a panel there covered the thing it was meant to sit beside. It grows upward, which keeps its toggle in one place as the tree gets longer. The panel is no longer rendered at all for a run with no container steps. It used to render as a permanently disabled toggle explaining there was no subtree - fine in a rail, but a floating panel that exists only to say it has nothing is worse than no panel. With the section behind that condition, the guards inside it became unreachable: a disabled state, an aria-expanded term and a tooltip that could never appear. Removed, so the markup stops describing a case that cannot happen. The page's test stub grew three methods so the viewer can actually render in it. That is what makes these assertions real rather than vacuous - the first attempt at the absence test passed against a deliberately broken template, because the patch that was supposed to break it never matched. 557 frontend tests green; both assertions fail when the condition is removed. 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.