Now I see what you mean. My IDE simply fixed the problem during the rename refactoring by adding `AnonymousTraversalSource.` for all calls to `Traversal()` where you're getting the error.
I had only inspected the changes in 2 classes manually and it worked in both. I think the problem is if the namespace of the test also includes the `Traversal` part. I guess it's ok to write those tests as: ```cs var g = AnonymousTraversalSource.Traversal().WithRemote(connection); ``` This doesn't really affect users as long as they don't also use the word _Traversal_ in their namespaces. One other idea in general for the change in this issue: What if we rename `AnonymousTraversalSource` to just `Graph` and then also don't recommend the `static using` here? This would result in: ```cs var g = Graph.Traversal().WithRemote(connection); ``` which is nearly the same as what we had before but a bit cleaner than: ```cs var g = new Graph().Traversal().WithRemote(connection); ``` Calling the method `Traversal()` without showing on what it is called looks a bit strange in general in my opinion. Just using a static class `Graph` and showing that `Traversal()` is a member of `Graph` avoids this. [ Full content available at: https://github.com/apache/tinkerpop/pull/968 ] This message was relayed via gitbox.apache.org for [email protected]
