update a test

typo

remove unecessered line on test_api_client

fix typo and errors

In D5707#144937, @vlorentz wrote:

What is the difference between nbEdgesAccessed and currentEdgeAccessed? It looks like the latter is not used at all (only incremented, but never read), but I may be missing something

I see that in multiple place, you set currentEdgeAccessed = 0; before breaking/returning. What is it for? Is the same instance of Traversal used to serve multiple queries?

change commit name

squash commits

• add all possible values for the request

fix argument in Entry and Traversal + an assert in test_api_client

squash commits

conflicts merge fixed

fix diff

• fix comment

rebase and add comments and examples in NodeFiltering class

• add comments and examples in NodeFiltering class

add comment and examples of queries

adding comments, tests, and fix code style

change commit name

squash

• max_edges argument was missing

• add the maxEdges parameter for leaves and neighbors endpoints

squash

maxEdges is now a Traversal parameter

squashing of commits

I fixed the unit tests that didn't work because of the default argument value of max_edges (it was None instead of 0) in graph.py

add an anti-Dos limit for edges traversed as a query parameter

fix + rebase

rebase

I'm not sure how to fix this problem. I just update the code and used "arc diff update..." etc

'max_edges' have now a default value (0 for no limit) which allow to simplify the java code

1/ So for the "filter that applies to visits that return nodes one by one" part, we are talking about: neighbors, walk, visit/nodes only?
2/ the filter is a query parameter I guess?

I have two questions to make sure I understand well :

complete the task on the right server and add tests

I thought we should group the code by endpoint type, all the "get" endpoints without arguments between them (we can consider them as default cases), as well as the "before" endpoints and the "get" endpoints with detailed arguments that were already coded. I may be wrong