The panel's three-way actions block had no test for its middle branch: an item with equipmentSlot null should show "Nicht ausrüstbar" and no equip button. The gap predates this slice -- Task 14's review found it while confirming the removed level gate had not cost coverage. Deferred until now on purpose: the web bundle could not compile for the whole slice, so committing this earlier would have meant shipping a test I had never executed. Load-bearing: dropping the !isEquippable() guard would fall through to the else branch and render the button, failing the assertion. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Web
This project was generated using Angular CLI version 21.2.6.
Development server
To start a local development server, run:
ng serve
Once 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-name
For a complete list of available schematics (such as components, directives, or pipes), run:
ng generate --help
Building
To build the project run:
ng build
This 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 test
Running end-to-end tests
For end-to-end (e2e) testing, run:
ng e2e
Angular 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.