Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a task tracker in modern Angular (v17+): standalone components (no NgModule), a root-provided service (@Injectable({providedIn:'root'})) holding the task list and injected with inject(), SIGNALS for state (read by calling them), the built-in @if/@for control flow (with track), and two-way binding to add tasks. Toggle done and show a computed() remaining count. Scaffold with the Angular CLI. No NgModule, no *ngIf/*ngFor.
Standalone components bootstrapped with bootstrapApplication; a providedIn:'root' service injected via inject(); no NgModule.
State in signals read with parentheses; @if/@for (with track) used, not *ngIf/*ngFor; a computed() for derived count.
Property/event/two-way binding used correctly to add and toggle tasks.
CLI-scaffolded, typed end to end, readable; no legacy NgModule/structural-directive patterns.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A standalone-component task tracker
## Goal
Build a task tracker in modern Angular (v17+): standalone components (no NgModule), a root-provided service (@Injectable({providedIn:'root'})) holding the task list and injected with inject(), SIGNALS for state (read by calling them), the built-in @if/@for control flow (with track), and two-way binding to add tasks. Toggle done and show a computed() remaining count. Scaffold with the Angular CLI. No NgModule, no *ngIf/*ngFor.
## Acceptance criteria
- [ ] Standalone + DI: Standalone components bootstrapped with bootstrapApplication; a providedIn:'root' service injected via inject(); no NgModule.
- [ ] Signals & control flow: State in signals read with parentheses; @if/@for (with track) used, not *ngIf/*ngFor; a computed() for derived count.
- [ ] Binding: Property/event/two-way binding used correctly to add and toggle tasks.
- [ ] Quality: CLI-scaffolded, typed end to end, readable; no legacy NgModule/structural-directive patterns.
## Verification
- [ ] Document installation and run commands.
- [ ] Record automated checks and their exact commands.
- [ ] Add representative output, screenshots, or a short demo where useful.
- [ ] Confirm failure paths and known constraints.
## Decision log
### Decision title
- Context:
- Choice:
- Alternatives considered:
- Tradeoffs:
## Evidence
- Link each rubric criterion to the file, test, or artifact that demonstrates it.
## Known limitations
- List what is intentionally out of scope and what should be improved next.