{"version":"2.1.299","anchor":"doc-update-and-project-read-carry-version-and-base-hash","canonical_anchor":"doc-update-and-project-read-carry-version-and-base-hash","heading":"Document updates can now carry a fingerprint of the version they were based on","tier":"notice","area":"Projects","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/doc-update-and-project-read-carry-version-and-base-hash","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Document updates can now carry a fingerprint of the version they were based on\n\nUpdating a project document can now send a fingerprint of the content it started from, and reading a project can return a version\n\n**What**\n\nTwo changes affect project documents:\n\n- Updating a document can now send a fingerprint of the content the edit started from. The fingerprint is a SHA-256 hash, a short code calculated from the text.\n\n- Reading a project can now return a version for what was read.\n\nPreviously, an update sent only the new content.\n\n**Why**\n\nThis lets an edit notice when the document changed after it was read, so one change does not silently overwrite another.\n\n- Area: Projects\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}