imbajin commented on code in PR #499:
URL: https://github.com/apache/hugegraph-doc/pull/499#discussion_r4173368801


##########
data/docs_nav.json:
##########
@@ -215,6 +215,15 @@
           "children": [
             {
               "page": "/docs/language/hugegraph-gremlin"
+            },
+            {
+              "page": "/docs/language/hugegraph-cypher"

Review Comment:
   ‼️ Blocking: yes. Summary: These new navigation entries change the generated 
metrics (latest page count and tree hash, plus each historical version's 
removed count and tree hash), but this PR leaves `DOCS_NAV_EXPECTED_STATS` 
unchanged. `validate_artifact()` compares generated `docsNavigation` against 
those pinned values, so the version builds will fail after the earlier OINK 
check; please regenerate and update the expected stats alongside these routes. 
Evidence: the new routes are added here and are null for historical versions in 
`data/version_routes.json`; exact-head `scripts/versioning.py` still pins 
latest `pages` at 91 and checks metadata at lines 3444-3447.



##########
content/en/docs/language/cypher-compatibility.md:
##########
@@ -0,0 +1,97 @@
+---
+title: "Cypher Compatibility"
+linkTitle: "Cypher Compatibility"
+weight: 3
+---
+
+### Scope
+
+**No statement on this page describes a released HugeGraph version.** A 
released build exposes exactly two

Review Comment:
   ⚠️ Blocking: no. Summary: The disclaimer says no statement on this page 
describes a released version, but the same paragraph immediately defines 
released API request forms and the table labels some forms as released. Please 
limit the disclaimer to the development-tree test results and keep the released 
behavior explicitly scoped. Evidence: lines 9-13 and the request-form table at 
lines 29-34.



-- 
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]

Reply via email to