TypeScript for Real Projects · 45 min · 320 XP

Capstone: release planner

Independently build a release planner that validates unknown tickets and produces a typed, immutable summary.

Independent capstone: use the brief as your specification. Sketch domain and result unions, write a validation checklist and predict edge cases before implementing. Reuse the ideas from earlier lessons without copying a complete solution. Run both browser tests and the local strict compiler workflow.

A release planner receives external ticket data and reports what is ready to ship. Separate three concerns in your design: establishing trusted tickets, deciding how each status affects the release, and projecting the public summary. A parser can validate one ticket, while the planner owns duplicate ids and totals. This separation makes a new status an explicit domain change.

Before considering the project complete, use the local strict compiler config. Add an expected-error example for a ready Ticket without points and for reading totalPoints before narrowing ReleaseResult. Extend your runtime examples with an all-blocked release. Then explain why a type assertion cannot replace parseTicket and how you would add a third status without silently skipping it.

Loading your workspace…