The first note in this demo restates the core promise from the announcement: fate keeps component data requirements co-located, then composes them into one request at the screen root. Instead of deciding when every component should fetch, you describe what each component needs. The result feels close to Relay fragments, but it stays in plain TypeScript with no GraphQL schema or query language to adopt.
- Christoph
Jamal
Search results and category pages sharing Post records is a good way to show the cache doing real work.
Dina
Seeing optimistic actions and live updates use the same normalized cache is the key idea.
Kai
The view-first framing is the clearest way I have seen to explain why request hooks create so much incidental state.