IDs are used to resolve state JSONs to existing nodes (such as @meta:SomeMetaNode). This is fine for user/programmatically created JSON (the initial purpose) but is a little more problematic when exporting to JSON as the identity is ambiguous. As of #10, exported JSON uses GUIDs. This avoids issues (such as exporting, moving a node, and re-syncing) but comes at a performance cost.
That said, there are other defaults that might be intelligent to have such as:
- using
@name:<name> for inherited children (structural inheritance)
- using
@meta:<name> for nodes that are not in the export but part of the meta
IDs are used to resolve state JSONs to existing nodes (such as
@meta:SomeMetaNode). This is fine for user/programmatically created JSON (the initial purpose) but is a little more problematic when exporting to JSON as the identity is ambiguous. As of #10, exported JSON uses GUIDs. This avoids issues (such as exporting, moving a node, and re-syncing) but comes at a performance cost.That said, there are other defaults that might be intelligent to have such as:
@name:<name>for inherited children (structural inheritance)@meta:<name>for nodes that are not in the export but part of the meta