Reconnexion/ng-eventually
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: la règle fondamentale devient toujours chargée, et la chaîne cesse d'être morte au sommet

Browse Source
This commit is contained in:
Sylvain Duchesne
2026-08-27 14:29:42 +02:00
parent f6a48a4507
commit 817f9074c4
8 changed files with 23 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.project/concepts/sign-in/knowledge_how-a-user-gets-in.md
+1 -1
View File
@@ -11,7 +11,7 @@ A newcomer holds nothing. To act they need a wallet imported once into the walle
Then the page is handed to the broker, which opens the wallet and reloads the application **inside an iframe it hosts**. Outside that iframe there is no session.
**The redirect is not ours.** `@ng-org/web`'s `init()` performs it as its first statement — same host, same URL shape, same frame check. Verified in its shipped bundle: when `window.self === window.top` it assigns `window.location.href` from a hard-coded `redirect` constant. This package must not reimplement it; doing so would double a function of the layer below and diverge from it in the meantime (see `app-contract/rule_no-divergence-from-nextgraph`).
**The redirect is not ours.** `@ng-org/web`'s `init()` performs it as its first statement — same host, same URL shape, same frame check. Verified in its shipped bundle: when `window.self === window.top` it assigns `window.location.href` from a hard-coded `redirect` constant. This package must not reimplement it; doing so would double a function of the layer below and diverge from it in the meantime (see `.project/rules/nextgraph/no-divergence-from-nextgraph.md`).
What is genuinely ours is the one thing `init()` cannot do: **put the identifier into the URL before `init()` reads it**. `init()` hands over `window.location.href`; it does not know the parameter exists.