Lucio Lelii
4fa449658e
Finalizing a flow makes it permanently read-only and cannot be undone, and it is not part of the current workflow, so the controls that create that state are now hidden: the Finalized toggle in the title toolbar and the Finalized entry in the flows list filter. Gated by FLOW_FINALIZATION_ENABLED, matching SWIMLANES_ENABLED, so nothing is deleted and re-enabling is one line. Only the controls are gated. The badge on a flow row, the disabled delete and the read-only editor stay, because rows finalized before the switch still exist and hiding the explanation of why such a flow cannot be edited would make the app inexplicable. For the same reason the toggle reappears for a flow that is already finalized, so its state is never invisible in the place that owns it. A persisted FINALIZED list filter now falls back to showing everything: a filter whose control is hidden would otherwise keep narrowing the list with nothing on screen to clear it. The backend is untouched - finalized still gates editing and deletion there. 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.