On the dashboard, the problem is that newly added entities might not get connected to existing entities (ie. ones already present in the dashbaord) if the in/outdegree of the new entity is bigger N (currently 100), because the list of neighbors is not fetched for them due to its length.
However, this could be improved by constraining the list of neighbors by the ones already present.
So, I'd propose to add an optional parameter to /entity/<entity>/neighbors which carries a list of target entity ids. The result then should be constrained to neighbor entitys of the given ids.
Due its potentially big length this parameter would need to be sent in the body of the request.
On the dashboard, the problem is that newly added entities might not get connected to existing entities (ie. ones already present in the dashbaord) if the in/outdegree of the new entity is bigger N (currently 100), because the list of neighbors is not fetched for them due to its length.
However, this could be improved by constraining the list of neighbors by the ones already present.
So, I'd propose to add an optional parameter to
/entity/<entity>/neighborswhich carries a list of target entity ids. The result then should be constrained to neighbor entitys of the given ids.Due its potentially big length this parameter would need to be sent in the body of the request.