ข้ามสารบัญไปยังเนื้อหา
อัปเดต 2026-09-07
Datasheet revision & persistence
shared, per-slug
A shared revision-history layer persists a calculator or case-study datasheet's edits server-side (one row per slug, an opaque revisions[]/activeRevId payload) so a Rev 0A vs. Rev 1 comparison survives across sessions and reviewers, instead of resetting to source defaults on every reload.
เมื่อไรจึงใช้
- Multiple reviewers (GB/admin) need to edit and compare datasheet revisions over time, not just within one browser session.
- A case-study datasheet needs a saved revision to persist even though the underlying calculator source defaults later change.
- You're diagnosing why a datasheet shows an old value after a source-code change — a saved revision may be overriding the new default.
ค่าที่ต้องกรอก
| ค่า | คำอธิบาย |
|---|---|
ข้อควรระวัง
noteA saved revision OVERRIDES source defaults — renaming or re-characterizing an underlying calculator in code has no effect on an already-saved revision until that revision is explicitly patched.
noteTwo people editing the same datasheet concurrently is last-write-wins on the whole payload — a long-open autosave session can silently overwrite a direct backend patch made in between.
ที่เกี่ยวข้อง