docs(requirements): add rings to async data rows
Add explicit northstar ring fields to async_data requirements and remove speculative wording without changing behavior. req: async_data/001 req: async_data/002 req: async_data/003
This commit is contained in:
+3
-3
@@ -915,13 +915,13 @@ what a valid business email is. [north_star]
|
||||
## async_data
|
||||
|
||||
### req: async_data/001
|
||||
001 If introduced, async remote data helpers live in optional `Resource<T>` / `Query<K, T>` / `Mutation<I, O>` integrations, not in v0 core. v0 server-first data loading is ordinary Rust/Axum code.
|
||||
0 001 Async remote data helpers live in optional `Resource<T>` / `Query<K, T>` / `Mutation<I, O>` integrations, not in v0 core. v0 server-first data loading is ordinary Rust/Axum code. [north_star]
|
||||
|
||||
### req: async_data/002
|
||||
002 `QueryEffect::reload(res)` triggers a re-fetch and re-render. The server sends a new `EffectBatch` when data is ready. Query/Resource effects live in a separate API surface to keep core small.
|
||||
0 002 `QueryEffect::reload(res)` triggers a re-fetch and re-render. The server sends a new `EffectBatch` when data is ready. Query/Resource effects live in a separate API surface to keep core small. [north_star]
|
||||
|
||||
### req: async_data/003
|
||||
003 If introduced, query helpers must compile to ordinary handlers and effects; they must not introduce a client-side data framework or cache as a core dependency.
|
||||
0 003 Query helpers must compile to ordinary handlers and effects; they must not introduce a client-side data framework or cache as a core dependency. [north_star]
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user