Nestsets association: element / vertex
Is there a reason/use case to allow both? I feel like they both specify the same thing, and by allowing both, it increases the processing and validation code needed. For example, I would need to globally validate that all are either vertex or element to make sure things make sense.
@nselliott for nesting, I think we expect element associated metadata? (Correct me if I am wrong :-) Any reason to not make that the only path for now?
@cyrush I recall that our original discussions envisioned allowing both, but element is the only one that is useful for my purposes, so that's fine if it make everything easier.
the association should still be present for clarity, but only one valid value.