amatiushkin commented on pull request #1485: URL: https://github.com/apache/tinkerpop/pull/1485#issuecomment-950378846
Ok. I think it make sense to introduce different strategies for importing default values. Given the impact of this change, I would propose following strategies: - default (interim) — defaults are not imported at all, similar to current implementation. - Gephi-like — default are imported like in Gephi (all defaults are assigned, unless overwritten) - explicit — only exact defaults are assigned (empty, self-closing nodes are ignored) - soft — empty and self-closing nodes are overwriting default values if possible - custom — user defines behavior as combination of above The list of exact features is not fully know to me, but I can highlight few things: - default value has been assigned to a node/edge - node/edge has data element which refers to a key with default value - data element in node/edge defines default value These features needs to be listed in a specification-like fashion in the documentation. I will propose draft, since I am busy with this anyway, but I absolutely need to collect your inputs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
