bitflicker64 commented on code in PR #557:
URL: https://github.com/apache/hugegraph-doc/pull/557#discussion_r4439903188


##########
content/en/docs/clients/restful-api/cypher.md:
##########
@@ -91,24 +90,87 @@ POST /graphspaces/{graphspace}/graphs/{graph}/cypher
 
 Note:
 
-> It is not in JSON format, but a plain text Cypher statement.
+> The request body contains the raw Cypher text statement rather than a JSON 
object. However, because the server endpoint uses 
`@Consumes(APPLICATION_JSON)`, requests must include `-H "Content-Type: 
application/json"` (requests sent with `text/plain` are rejected with HTTP 415).

Review Comment:
   R3 status at `8faa8816`: **fixed**. The note now says "raw Cypher string (a 
JSON object body is also accepted; see 9.1.3)" in EN and CN.



##########
content/en/docs/clients/client/hugegraph-client.md:
##########
@@ -167,7 +556,7 @@ The constraint information that PropertyKey allows to 
define includes: name, dat
 
|------------------------------------|------------------------------------------------|
 | userdata(String key, Object value) | The same key, the latter will cover the 
former |
 
-##### 2.2.2 Create PropertyKey
+##### 6.2.2 Create PropertyKey

Review Comment:
   R3 status at `8faa8816`: **partly fixed**. The 2.x and later subsection IDs 
are pinned, for example `{#222-create-propertykey}` and `#222-创建-propertykey`. 
Legacy IDs from the former quickstart page are still missing: 
`#1-hugegraph-client`, `#11-builder-options`, `#12-operation-entries` and 
`#5-simple-example`, now sections 5.1 and 5.2 around lines 423 and 448, plus 
the CN equivalents.



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