d3cba7acee
Make @docmost/git-sync natively consumable by the CommonJS server (and jest):
build to CommonJS (tsconfig module CommonJS, drop type:module, strip .js from
relative imports), and lazy-load the only ESM-only dep (marked) via the dynamic
Function('import()') trick (mirrors docmost-client.loader.ts) with a require()
fallback so vitest's evaluator works too. git-sync tests stay green (314 pass,
3 expected fail).
Add the §13.1 idempotency gate (apps/server .../git-sync-converter-gate.spec.ts):
13 editor-ext docs (paragraphs/headings, marks, links, bullet/ordered/task lists,
blockquote, callouts, code block, hr, table, nested mix) round-trip
content(editor-ext) -> convertProseMirrorToMarkdown -> markdownToProseMirror ->
TiptapTransformer.toYdoc/fromYdoc(tiptapExtensions) -> canonicalize and assert
docsCanonicallyEqual. All green => the vendored converter's docmost-schema is
schema-compatible with editor-ext (no node/mark/attr loss), which the plan §13.1
requires before Phase B. The one intrinsic markdown-image lossiness (width/height
/align can't ride plain ) is isolated in a KNOWN DIVERGENCE block, not
hidden. Server tsc clean.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
32 lines
1.7 KiB
JavaScript
32 lines
1.7 KiB
JavaScript
"use strict";
|
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
exports.bodyHash = bodyHash;
|
|
/**
|
|
* Loop-guard primitives (SPEC §10). The sync engine must never re-pull its OWN
|
|
* write as if it were a remote edit: after a push, the next poll will see the
|
|
* page it just wrote with a fresh `updatedAt`. To suppress that, we key on two
|
|
* signals — the body HASH of what we pushed (this module) and the `updatedAt`
|
|
* returned by the write — recorded per page at push time.
|
|
*
|
|
* This module owns the PURE, deterministic body-hash. The CONSUMPTION on the
|
|
* pull side (comparing an incoming page's body hash against the last pushed hash
|
|
* to decide "this is our own write, ignore it") is a future increment — here we
|
|
* only PRODUCE the hash and the per-page push record (see `src/push.ts`).
|
|
*/
|
|
const node_crypto_1 = require("node:crypto");
|
|
/**
|
|
* Stable hash of a page's markdown BODY (SPEC §10 "хэш тела"). Deterministic:
|
|
* the same input string always yields the same digest, a different input a
|
|
* different one. Used to recognize our own write later (loop suppression).
|
|
*
|
|
* We hash the body STRING as-is (UTF-8) with SHA-256 and return lowercase hex.
|
|
* SPEC §10 keys on the body hash rather than file bytes; callers decide WHAT
|
|
* counts as "the body" (here it is the exact string passed in — typically the
|
|
* self-contained markdown that was pushed). No normalization is applied: the
|
|
* caller is responsible for passing a canonical/stable representation if it
|
|
* wants hash equality across cosmetic-only differences.
|
|
*/
|
|
function bodyHash(markdownBody) {
|
|
return (0, node_crypto_1.createHash)("sha256").update(markdownBody, "utf8").digest("hex");
|
|
}
|