Repository navigation
docs: clarify Go schema and status handling - #516
Merged
Merged
Conversation
- document nil and empty edge label properties - distinguish HTTP status from Go request errors - check HTTP and Gremlin status in the example
MrJs133
approved these changes
Oct 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Go guide lists edge-label creation without explaining that nil or empty properties are valid, and its Gremlin example reads data after checking only
err. Explain the schema contract and check both HTTP and Gremlin status before using results in the English and Chinese guides.Paired code PR: ASF #807. Coordinate the documentation merge with the code PR.
Validation: unchanged link validator, diff checks, bilingual example compilation and a fresh latest strict build passed with cached Hugo 0.165 Extended, Python 3.13 and WebP tools. Generated pages contain the new guidance and status checks. Independent documentation review passed.
Source org PR: #43. This uses the same source branch and commit after the current-head org site checks pass.
Change diagram
Propertyless edge labels and layered HTTP/Gremlin status checks in the Go client guide. This conceptual diagram supplements the bilingual examples above.
