fix bug where listProperties couldn't be overridden

Author: mpollmeier

gremlin-scala/src/main/scala/gremlin/scala/ScalaVertex.scala

@@ -27,9 +27,19 @@ case class ScalaVertex(vertex: Vertex) extends ScalaElement[Vertex] {
     vertex
   }
 
-  override def removeProperty(key: Key[_]): Vertex = {
-    val p = property(key)
-    if (p.isPresent) p.remove()
+  override def removeProperty(key: Key[_]): Vertex =
+    removeProperty(key, Cardinality.single)
+
+  def removeProperty(key: Key[_], cardinality: Cardinality): Vertex = {
+    cardinality match {
+      case Cardinality.single =>
+        val p = property(key)
+        if (p.isPresent) p.remove
+      case Cardinality.list | Cardinality.set =>
+        vertex.properties(key.name).asScala.foreach { p: VertexProperty[_] =>
+          p.remove
+        }
+    }
     vertex
   }
 
@@ -114,7 +124,7 @@ case class ScalaVertex(vertex: Vertex) extends ScalaElement[Vertex] {
 
   /** convenience function for `property` which normally requires to pass in key/value pairs as varargs */
   def setPropertyList[A <: AnyRef](key: String, values: List[A]): VertexProperty[A] = {
-    removeProperty(Key[A](key))
+    removeProperty(Key[A](key), Cardinality.list)
     values
       .map { value =>
         vertex.property(Cardinality.list, key, value)

gremlin-scala/src/test/scala/gremlin/scala/ElementSpec.scala

@@ -66,6 +66,10 @@ class ElementSpec extends TestBase {
       // gremlin-scala style
       v.setPropertyList(TestProperty, List("one", "two", "three"))
       graph.V(v).properties(TestProperty.name).count.head shouldBe 3
+
+      // can override
+      v.setPropertyList(TestProperty, List("three", "four"))
+      graph.V(v).properties(TestProperty.name).count.head shouldBe 2
     }
 
     it("removes a property") {