Repository navigation
Conversation
- use configured graph space in existing schema APIs - preserve legacy routes for empty graph spaces - retain request and HTTP error semantics - cover route escaping and request bodies with race
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 59 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Purpose of the PR
The Go client accepted GraphSpace configuration for vertex/Gremlin requests but ignored it in schema requests. Existing schema operations now route to the configured space; an empty space retains the legacy path.
Found in the Toolchain integration report.
Main Changes
Verifying these changes
go test -race -count=1 -timeout 30s ./api/v1/... -run '^TestSchemaGraphSpaceRoutes$' -vpasses.Does this PR potentially affect the following parts?
Documentation Status
Doc - TODODoc - DoneDoc - No Need: fixes the behavior of the existing GraphSpace configuration.