Restore the checked web application framework - #33
Conversation
|
Important Review skippedToo many files! This PR contains 114 files, which is 14 over the limit of 100. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (116)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Restores Uhura's web application meta-framework on top of the 0.4 machine-first language, without adding a compatibility frontend.
[framework]web-appprofile and one shared project resolverApplicationmodulesCloses #27.
Why
The 0.4 machine rewrite deliberately focused on the kernel and left the previous filesystem application topology behind. Application structure consequently lived in one large authored module, while the CLI and host retained overlapping ideas about project discovery.
This change restores application ergonomics as a checked compilation layer. Authored files remain modular and human-facing; the runtime still receives one deterministic, globally checked program.
Contract
A framework project opts in explicitly:
The first version deliberately excludes layouts, slots, loaders, component-local state, lifecycle hooks, and a second scheduler. Pure UI components use typed props and emitted events; application state and transitions remain machine-owned.
Validation
cargo fmt --all -- --checkcargo clippy --locked --workspace --all-targets -- -D warningscargo test --locked --workspace --all-targetscorepack pnpm@10.11.0 -C web check— 283 passed, 2 skippedbash scripts/build-wasm.shThe Spock integration check continues to report its existing intentional warning for the unchecked provider adapter.