I am getting primary label errors when I try to use a generic class in my model
@Transient
open class PropNode<T> (
open var value: T? = null,
open var deletedValue: T? = null,
@DynamicLabels
open var labels: Collection<String>,
): Entity()
will generate the error
The schema already contains a node description under the primary label PropNode
Does the mapper create multiple classes from the generic class when it parses the other classes that call the generic and the run into conflicts because each concrete has the same primary label? If so I was under the impression the @Transient label would prevent that.
Any thoughts or help?
