Exercise 3: Why StaticFiles Is This Course's SPA-Fallback Equivalent, and Why Order Still Matters — Possible Solution
====================================================================

WHY IT'S THE EQUIVALENT OF THE EXPRESS COURSE'S FALLBACK ROUTE
------------------------------
Both mechanisms exist to serve the frontend's own entry point in response to a request the backend doesn't otherwise have a specific route for. Food Tracker (React + Express) had to hand-write a catch-all route returning index.html for anything unmatched, so React Router could take over client-side. Here, StaticFiles(directory="static", html=True) does the same underlying job - serving files out of the static directory, including automatically returning index.html for unmatched paths - just configured as a single constructor argument rather than a hand-written route.

WHY /api/health IS STILL REGISTERED FIRST, EVEN WITHOUT A CLIENT-SIDE ROUTER
------------------------------
A Mount, like app.mount("/", StaticFiles(...)), claims an entire path prefix - mounted at "/", it would match any path at all, including /api/health, if it were registered before that route. FastAPI (built on Starlette) evaluates registered routes in order, the same as Express does - so the same underlying risk exists here: a route registered after a Mount that already covers its path can end up shadowed by it. Registering the API route first, exactly as this chapter's own main.py does, avoids that risk here for the same underlying reason Chapter 11 of the Express course gave for its own catch-all - not because FastAPI is somehow exempt from the concern, but because the same discipline (specific routes before catch-all-shaped ones) still applies.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains the functional equivalence between StaticFiles(html=True) and the Express course's own hand-written fallback route, and correctly identifies that route registration order still matters here for the same underlying reason it did in the Express course, rather than assuming FastAPI's built-in mechanism is automatically safe from the same class of problem.