Base class for our DSL These are the base steps available in all steps of the query language. There are no constraints on the element types, unlike e.g. NodeSteps
- Companion
- object
Value members
Concrete methods
Execute the traversal and convert it into a Java list (as opposed to the Scala list obtained via toList)
Execute the traversal and convert it into a Java list (as opposed to the Scala list obtained via toList)
Execute this traversal and pretty print the results. This may mean that not all properties of the node are displayed or that some properties have undergone transformations to improve display. A good example is flow pretty-printing. This is the only three of the methods which we may modify on a per-node-type basis, typically via implicits of type Show[NodeType].
Execute this traversal and pretty print the results. This may mean that not all properties of the node are displayed or that some properties have undergone transformations to improve display. A good example is flow pretty-printing. This is the only three of the methods which we may modify on a per-node-type basis, typically via implicits of type Show[NodeType].
Execute the traversal and convert it to a mutable buffer
Execute the traversal and convert it to a mutable buffer
Execute traversal and convert the result to json. toJson (export) contains the exact same information as
toList, only in json format. Typically, the user will call this method upon inspection of the results of
toList in order to export the data for processing with other tools.
Execute traversal and convert the result to json. toJson (export) contains the exact same information as
toList, only in json format. Typically, the user will call this method upon inspection of the results of
toList in order to export the data for processing with other tools.
Execute traversal and convert the result to pretty json.
Execute traversal and convert the result to pretty json.