ChurchServe Angular Tutorial Part 14: Route Guards, Resolvers, and Unsaved Changes
Coordinate protected ChurchServe routes, preloaded event data, redirects, and unsaved form warnings with testable router functions.
Coordinate protected ChurchServe routes, preloaded event data, redirects, and unsaved form warnings with testable router functions.
Add a server-managed cookie session, antiforgery protection, sign-in UI, session restoration, and authenticated API tests to ChurchServe.
Extract accessible Angular panels and empty states with named content projection while keeping ChurchServe business behavior inside its feature components.
Create a shareable ChurchServe schedule whose month, ministry, and page live in the URL and drive a filtered, paginated ASP.NET Core API query.
Build responsive Angular volunteer search with runtime DTO validation, debouncing, switchMap cancellation, explicit request state, retry behavior, and deterministic tests.
Extend the ChurchServe API with normalized volunteer data, SQLite seeding, a cancellable search endpoint, and integration tests.
Scaffold a runnable ASP.NET Core API for ChurchServe, persist service events with EF Core and SQLite, proxy Angular requests, and verify the endpoints with integration tests.
Replace ChurchServe’s browser-only repository with a typed Angular HttpClient implementation, runtime DTO validation, explicit request states, and focused HTTP tests.
Persist the beginner ChurchServe schedule in localStorage with schema versioning, runtime validation, migration, recovery, and storage-focused unit tests.
Move ChurchServe data access behind an Angular repository contract and dependency injection without adding storage concerns too early.