Paddy
e8d2dc2901
From the same pre-deploy review. None of the four write calls had an error callback, so a failure closed the row and saved nothing while looking exactly like success. That was survivable when the session was a localStorage value this app controlled; after the cutover a 401 is routine - the session expires, or is ended from another app or another tab - so silence is not. A 401 now says so and goes to the login carrying this page as the return target; everything else says what happened and leaves the edits on screen. getEvents had the same gap, and it is the one that matters during the deploy itself: between the API going out and this bundle following it, the old code renders as signed in and shows an empty table, which reads as "the calendar lost its data" rather than "a deploy is in progress". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
NachklangCalendar
This project was generated with Angular CLI version 14.2.1.
Development server
Run ng serve for a dev server. Navigate to http://localhost:4200/. The application will automatically reload if you change any of the source files.
Code scaffolding
Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Build
Run ng build to build the project. The build artifacts will be stored in the dist/ directory.
Running unit tests
Run ng test to execute the unit tests via Karma.
Running end-to-end tests
Run ng e2e to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.
Further help
To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.