When exporting the tree or project as json, whilst the custom nodes is output as an array (which makes sense) all the contents of 'nodes' is flattened into attributes under respective ids.
Whether or not the json format were updated to reflect the tree structure (i.e. children within parents), it would be helpful to have the nodes reflected again as an array. At the moment it seems like it needlessly makes it more difficult for the export to be parsed?
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/30110605-json-export-format-inconsistent?utm_campaign=plugin&utm_content=tracker%2F18331319&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F18331319&utm_medium=issues&utm_source=github).
When exporting the tree or project as json, whilst the custom nodes is output as an array (which makes sense) all the contents of 'nodes' is flattened into attributes under respective ids.
Whether or not the json format were updated to reflect the tree structure (i.e. children within parents), it would be helpful to have the nodes reflected again as an array. At the moment it seems like it needlessly makes it more difficult for the export to be parsed?