Repository navigation
feat(site): read server state through effect-atom runtime atoms - #98
Open
systemfsoftware-maker wants to merge 1 commit into
Open
systemfsoftware-maker wants to merge 1 commit into
systemfsoftware-maker wants to merge 1 commit into
Conversation
The guestbook page and the home page built RPC effects inside .tsx modules and ran them with Effect.runPromise from useEffect and event handlers. Server calls now live in .ts atom modules on one runtime over the RPC client layer (api/health-atoms.ts, features/guestbook/ guestbook-atoms.ts): query atoms for list and health, fn atoms for sign and moderate that refresh the list, and pure view functions composed into server-safe view atoms. Components only read atoms and dispatch; the root route binds the client layer into the registry once. Adds @systemfsoftware/effect-atom and effect-atom-react from the flake's .sfs-deps tarballs. Follows the ui-state pack (components-perform-no-io, server-data-lives-in-atoms, components-dispatch-to-runtime-atoms, view-models-are-pure-functions).
systemfsoftware-maker
added this pull request to stack #100
October 16, 2026 04:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The guestbook page and the home page built RPC effects inside .tsx
modules and ran them with Effect.runPromise from useEffect and event
handlers. Server calls now live in .ts atom modules on one runtime over
the RPC client layer (api/health-atoms.ts, features/guestbook/
guestbook-atoms.ts): query atoms for list and health, fn atoms for sign
and moderate that refresh the list, and pure view functions composed into
server-safe view atoms. Components only read atoms and dispatch; the root
route binds the client layer into the registry once.
Adds @systemfsoftware/effect-atom and effect-atom-react from the flake's
.sfs-deps tarballs. Follows the ui-state pack (components-perform-no-io,
server-data-lives-in-atoms, components-dispatch-to-runtime-atoms,
view-models-are-pure-functions).
Verification
Gates exit 0; site test 63; journeys 8/8 against pnpm dev; no runPromise/runFork/fetch in any .tsx.
Layer of stack #100 (trunk
main), merge bottom-up.