No hand-written HTTP handler, no fetch, no JSON glue, no route strings, no external deps. (Part 7 of the FitzLiveViews series — the "whole stack, no plumbing" moment.) Earlier parts showed a.fitzv component compiling two ways: to server-rendered HTML (LiveViews over a WebSocket) and to a standalone WebAssembly SPA.
No hand-written HTTP handler, no fetch, no JSON glue, no route strings, no external deps.
Anything real — reading the database, checking a token — has to happen on the server, and the classic bridge is plumbing: write an endpoint, write a fetch, marshal the JSON both ways, and keep the types in...
(Part 7 of the FitzLiveViews series — the "whole stack, no plumbing" moment.) Earlier parts showed a.fitzv component compiling two ways: to server-rendered HTML (LiveViews over a WebSocket) and to a...
The page is ready to read now. The fuller skim-friendly version will appear here automatically.
No hand-written HTTP handler, no fetch, no JSON glue, no route strings, no external deps. (Part 7 of the FitzLiveViews series — the "whole stack, no plumbing" moment.) Earlier parts showed a.fitzv component compiling two ways: to server-rendered HTML (LiveViews over a WebSocket) and to a standalone WebAssembly SPA. Anything real — reading the database, checking a token — has to happen on the server, and the classic bridge is plumbing: write an endpoint, write a fetch, marshal the JSON both ways, and keep the types in sync by hand.
Both are great — but a component in the browser is an island. This part erases all of that with one decorator.
Open the app view to save this story, compare related coverage, and continue from the same source.