Skip to content

fix: reload development sources atomically before HTTP dispatch - #14

Merged
WilliamRagstad merged 1 commit into
codex/route-specificity-20261025from
codex/html-reload-20261025
Oct 25, 2026
Merged

WilliamRagstad merged 1 commit into
codex/route-specificity-20261025from
codex/html-reload-20261025

Conversation

@WilliamRagstad

Copy link
Copy Markdown
Member

After a valid development save, the next request now sees the edited HTML without waiting for a watcher notification. Reconcile source contents before dispatch and publish the new route/module snapshot only after parsing, route validation, and global initialization succeed. Failed edits retain the complete last good snapshot. HTML-only changes preserve globals; changed global code resets its module.

PR 3 of 4; depends on the routing PR. Refs #7. Covers atomic-save renames, additions, deletions, and UTF-8 HTML. Watcher events request reconciliation instead of parsing partial event paths. Unterminated blocks now produce diagnostics.

Validation: cargo test --locked — 8 passed. Reload assertions make the next request immediately, without sleeps or polling. Production module behavior and per-call static file reads are also covered.

@WilliamRagstad
WilliamRagstad marked this pull request as ready for review October 25, 2026 22:15
@WilliamRagstad
WilliamRagstad merged commit 8825df4 into codex/route-specificity-20261025 Oct 25, 2026
1 check passed
@WilliamRagstad
WilliamRagstad deleted the codex/html-reload-20261025 branch October 25, 2026 22:15
@WilliamRagstad
WilliamRagstad restored the codex/html-reload-20261025 branch October 26, 2026 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant