tmk241/hemx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(requirements): add rings to client-local rows

Browse Source 
Add explicit northstar ring fields to client_local requirements and remove illustrative syntax wording without changing behavior.

req: client_local/001

req: client_local/002

req: client_local/003

req: client_local/004
This commit is contained in:
slhx agent
2026-06-25 17:12:25 +02:00
parent a787e5473a
commit 7ed44038d7
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
REQUIREMENTS.md
+4 -4
View File
@@ -899,16 +899,16 @@ what a valid business email is. [north_star]
## client_local
### req: client_local/001
001 Client-local handlers use the same function shape as server handlers. Opting into a client-local backend changes where the handler executes, not the authoring model.
0 001 Client-local handlers use the same function shape as server handlers. Opting into a client-local backend changes where the handler executes, not the authoring model. [north_star]
### req: client_local/002
002 Local UI state may live as ordinary fields on the app/component state. `Atom<T>` is required only when the value must be addressed by effects, bootstrapped, synced, or subscribed.
0 002 Local UI state may live as ordinary fields on the app/component state. `Atom<T>` is required only when the value must be addressed by effects, bootstrapped, synced, or subscribed. [north_star]
### req: client_local/003
003 High-frequency UI handlers (drag, pointermove, animation tick) must not require server round-trips or handwritten JS.
0 003 High-frequency UI handlers (drag, pointermove, animation tick) must not require server round-trips or handwritten JS. [north_star]
### req: client_local/004
004 The exact opt-in syntax for client-local handlers is not part of hemx-core v0. `#[hemx::handler(client)]` is illustrative; final syntax belongs to `hemx-wasm` integration.
0 004 Client-local handler opt-in syntax is an integration contract, not hemx-core v0; `hemx-wasm` owns concrete handler attributes. [north_star]
---