n24q02m commented on PR #499: URL: https://github.com/apache/hugegraph-doc/pull/499#issuecomment-5842965483
# Draft reply — apache/hugegraph-doc PR #499 (DO NOT POST; posting is user-gated) Post as PR comment. Imbajin first, then the new review threads. @-mentions: @imbajin @bitflicker64 (Copilot has no notifications; its threads still get per-thread answers below). --- ## Reply to @imbajin (2026-09-26, code-fence comment) @imbajin Thanks for catching this — fixed in 3599a2b. Every example fence in `hugegraph-cypher.md` now contains exactly one statement, in both EN and CN: - the aggregation fence you flagged → split into two labeled fences (`content/en/docs/language/hugegraph-cypher.md:111` and `:116`; CN mirror at the same lines); - the Read / Create / Delete fences had the same shape (multiple statements grouped in one block), so they were split the same way for consistency with the "single statement per request" rule. No wording changes elsewhere in the page. ## Reply to the 2026-09-26 review threads **1. `EXPLAIN` tip vs. compatibility record (`hugegraph-cypher.md:133`, EN + CN) — fixed in 3599a2b.** The tip no longer presents `EXPLAIN` → `result.data[0].translation` as a guaranteed response contract. It now says the statement is parsed with the `EXPLAIN` option and the translated Gremlin is *expected* in `result.data[0].translation` — translator-level behavior, not yet verified end-to-end on a server — with a link to the compatibility notes. `PROFILE` remains unsupported. **2. "`apache/hugegraph#238` URL returns 404" (6 threads: `cypher-compatibility.md:58`, `hugegraph-cypher.md:126`, `migrate-from-neo4j.md:31`, plus the CN mirrors) — no change; the cited URL does not exist on this branch.** All `#238` links in the three pages point to `https://github.com/hugegraph/hugegraph/pull/238` (verified open: "fix(cypher): support bound queries safely"). `apache/hugegraph#238` appears nowhere in the changed files, so there is no broken link to fix. If the bot reviewed an intermediate revision where the link was worded differently, the current head supersedes it. ## Where we intentionally did NOT change - `migrate-from-neo4j.md:45` / CN `:43` — the second Loader mention links to the GitHub `apache/hugegraph-toolchain/tree/master/hugegraph-loader` directory; the link is live (repo active, default branch `master`), and no review finding targets it. The in-doc Loader link that was flagged earlier (`/docs/quickstart/toolchain/hugegraph-loader/`) is already in place at line 34/33. - `data/*.json` — untouched by this round; the 2026-09-25 sort-order fix is already in the tree. - Compatibility/migration page content — the 2026-09-26 threads raise no new factual issue beyond the two items above. ## Already-resolved prior wave (context only) The 16 review threads from 2026-09-24/25 (bitflicker64 ×4: matrix rows for `MERGE ... ON CREATE/ON MATCH SET`, `=~`, `NOT ... IN`, EXPLAIN/PROFILE split, `$param` null-evaluation caveat, Loader link; Copilot ×10: CN mirrors, PR-description scope, `version_routes.json` ordering; imbajin ×2: Gremlin-fallback scoping, "draft" label) were all addressed in commit debb31848 ("docs: address cypher page review feedback") with per-thread replies posted on 2026-09-25. The PR description was re-scoped to the verification-record format, dropping the per-row evidence-tier promise. This push (3599a2b) only adds the 2026-09-26 fixes above. ## Commit / readback - Branch: `docs/cypher-language-page-2205` (fast-forward `debb31848..3599a2bdf`, no force) - Head: `3599a2bdf5d623658012841c8ceaaa6932e5fae1`, sha256 `97a731882abb24249dce156ab9a4751c9ead5081ee157da86c4dfc5bc84bdb66` - PR readback: `headRefOid == 3599a2bdf5d623658012841c8ceaaa6932e5fae1`, OPEN, MERGEABLE - Files touched: `content/en/docs/language/hugegraph-cypher.md`, `content/cn/docs/language/hugegraph-cypher.md` (+15/−1 each) - Checks: internal-link check PASS (both locales), fence balance PASS, EN/CN parity PASS (21 statement lines identical), zero multi-statement fences after split - Nothing posted upstream; all replies above are drafts awaiting approval. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
