Working copy and publishing for guides (#106) #112
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
MassiveDynamic/kataba!112
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/106-working-copy-and-publish"
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?
Closes #106
Edits to a published guide now go to its working copy. Readers, editors included, keep seeing the latest version until someone publishes again.
What changes
GuideVersion: a JSON snapshot plus who published it, when, and an optional note. Protective equipment (#95) counts as content./mediaall read the latest version./guides/<id>/preview. Guests get a 404 there, andpreviewis now a reserved slug.ensureFirstVersions,src/instrumentation.ts), so MySQL and MariaDB don't each need their own SQL JSON building.Tests
workingCopy.spec.access.specis adjusted to the new behaviour, and theauthoring.speclocator that had been failing since #90 is fixed.workingCopy.specwere rerun.🤖 Generated with Claude Code