imbajin commented on code in PR #3159:
URL: https://github.com/apache/hugegraph/pull/3159#discussion_r3804408263


##########
hugegraph-server/hugegraph-api/src/main/java/org/apache/hugegraph/auth/HugeGraphAuthProxy.java:
##########
@@ -2461,4 +2518,36 @@ public String toString() {
             return this.origin.toString();
         }
     }
+
+    private static Set<HugePermission> traversalPermissions(
+                                       Traversal.Admin<?, ?> traversal) {
+        Set<HugePermission> permissions = EnumSet.noneOf(HugePermission.class);
+        collectTraversalPermissions(traversal, permissions);
+        return permissions;
+    }
+
+    private static void collectTraversalPermissions(
+                        Traversal.Admin<?, ?> traversal,
+                        Set<HugePermission> permissions) {
+        for (Step<?, ?> step : traversal.getSteps()) {
+            if (step instanceof AddVertexStartStep ||

Review Comment:
   Final API-compatibility adjustment in f38b4ad6: the reflective test factory 
now prefers the official TinkerPop 3.7.6 merge constructor `(Traversal.Admin, 
boolean)` with `isStart=true`, and onMatch/child setup uses 
`addChildOption(Merge.onMatch, Traversal.Admin)` when the real `Merge` enum 
exists. Only the version-bound 3.5.1 fixture path falls back to its test-only 
`addChild` API; those fixtures now expose the official two-argument 
constructor, so current tests exercise constructor selection deterministically. 
Focused result remains 28/28; targeted API/test Checkstyle passed; main JAR 
exact merge fixture count remains 0.



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