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

docs(requirements): split app registry row

Browse Source 
Add explicit ring fields to derive_app requirements and split app registry singleton constraints without changing behavior.

req: derive_app/001

req: derive_app/002
This commit is contained in:
slhx agent
2026-06-25 17:55:07 +02:00
parent c7ca3aab9d
commit dceda8fdce
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
REQUIREMENTS.md
+4 -1
View File
@@ -1136,7 +1136,10 @@ async fn delete(app: State<App>, todo_id: TodoId) -> impl IntoEffect
## derive_app
### req: derive_app/001
001 `#[hemx::app(...)]` marks an application/root registry entry point and composes generated component handler modules into one app registry from the app state. There may be one registry per app/root type, and multiple runtime instances may exist per process. hemx does not require a process-global singleton or handwritten chains of per-component registration calls in canonical app code.
0 001 `#[hemx::app(...)]` marks an application/root registry entry point and composes generated component handler modules into one app registry from the app state.
### req: derive_app/002
0 002 There may be one registry per app/root type, and multiple runtime instances may exist per process; canonical app code avoids process-global singletons and handwritten per-component registration chains.
---