Hi! When using TraversalDescription.evaluator(), are there any guarantees regarding in which order the evaluators will be executed?
My use case is that I have a base TraversalDescription which excludes the start position using Evaluators.excludeStartPosition(). Then I discovered that other TraversalDescriptions built from this one still need to take care of evaluating the start position. This fact was hidden because of that the traversal didn't throw any expection when invoking methods on the last relationship traversed, even when the last releationship was in fact null. (I checked that my code actually throws a NPE ... but the traverser swallows that one.) I just don't like having to take care of the start position special case in each evaluator - is there any nice way I can avoid this? /anders _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
