RuDS is missing the forced re-render of bDS2 #106
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
bDS2 had the full render and the forced full render, where the forced full render did not look at hashes and always rebuilt the full blog with all files. That function was available through the blog menu with its own hotkey. we want that for RuDS, too. also needs to be updated in the RuDS allium spec, so that it is properly definedl.
Make sure that both the full render and the forced full render behave the same as they did in bDS2.
Implemented in commit
2844ed5. Added a distinct forced full-render mode across the native Blog menu (Cmd/Ctrl+Shift+R), desktop task workflow, CLI render --force, TUI force-render, all five render sections, bundled assets, and Pagefind. Normal rendering now matches bDS2 by trusting a matching stored content hash when the output exists; forced rendering ignores hashes, atomically rewrites every output, upserts current hashes, and preserves unrelated cache records. Updated all five UI locales, README, user documentation, and specs/generation.allium. Verification: cargo fmt --all; cargo clippy --workspace --all-targets -- -D warnings; cargo test --workspace; cargo build --workspace; allium check specs; cargo bundle-macos; real repository release bundle inspection confirmed the native menu order and clean shutdown. Neutral review against this issue, bDS2, and the Allium spec found no remaining gap.