Add 'direction' server option to specify which graph directions should be loaded into memory (forward|backward|both) defaulting to 'both' of not providedCurrently, the server loads both the forward and the transposed graphs into memory.
Pass direction parameter to Graph constructor and load the directions into memory conditionallyAdded `direction` server option to specify which graph directions should be loaded into memory `(forward|backward|both)` defaulting to `both` of not provided.
If a single direction was loaded, the direction in the query defaults to the loaded one.
Pass 'both' direction wherever a graph was constructed. Not adding an overload which defaults to 'both', because having to explicitly set the value makes you assess which option fits best.
Throw exception, if the loaded direction doesn't match queryIf the user queries the direction, or transpose/symmetrize is called on a singlethat was not loaded graph., If only single direction is loaded default the query param to chosen direction.
Add tests for forward/backward loaded directionsthe server response reflects that.