Adding back-end support for UI filters

[aai/sparky-be.git] / src / main / java / org / onap / aai / sparky / viewandinspect / entity / RelationshipDirectionality.java

diff --git a/src/main/java/org/onap/aai/sparky/viewandinspect/entity/RelationshipDirectionality.java b/src/main/java/org/onap/aai/sparky/viewandinspect/entity/RelationshipDirectionality.java
index 6ceede3..5104072 100644 (file)
--- a/src/main/java/org/onap/aai/sparky/viewandinspect/entity/RelationshipDirectionality.java
+++ b/src/main/java/org/onap/aai/sparky/viewandinspect/entity/RelationshipDirectionality.java
@@ -25,12 +25,10 @@ package org.onap.aai.sparky.viewandinspect.entity;
 /**
  * This enumeration is intended to be used to help us discriminate neighbor relationships for the
  * purpose of visualization and conceptualization to model in/out relationships between
- * ActiveInventoryNodes.
- * Possible visualization behaviors could be the following: - IN ( draw a line with 1 arrow ) - OUT
- * ( draw a line with 1 arrow ) - BOTH ( draw a line with 2 arrows, or 2 lines with 1 arrow each ) -
- * UNKNOWN ( draw a line with no arrows )
- * The UNKNOWN case is what we have at the moment where we have a collection neighbors with no
- * knowledge of relationship directionality.
+ * ActiveInventoryNodes. Possible visualization behaviors could be the following: - IN ( draw a line
+ * with 1 arrow ) - OUT ( draw a line with 1 arrow ) - BOTH ( draw a line with 2 arrows, or 2 lines
+ * with 1 arrow each ) - UNKNOWN ( draw a line with no arrows ) The UNKNOWN case is what we have at
+ * the moment where we have a collection neighbors with no knowledge of relationship directionality.
  * 
  * @author davea
  *