The output is definitely much better! Still some issues though e.g. the new "Donkey" tag didn't have a value change from 1 to 888; it was created with value 888. This becomes more significant the more complex the json is
Just for reference, this is how it's displayed in Git:
However, if I change the New's AreaC tags, I then get a bunch of changes that I don't want to see (AreaC was added; tags have not "changed" within it, they were created like that so they shouldn't be flagged as changes from the original, but rather complete and separate additions)
Perhaps the most significant drawback though, is that you don't know what the tagpath of the tag you're comparing is without backtracking up the structure and manually piecing together the folder names. This could be almost impossible for a full tag export, and a significant brain drain when there are many changes.
New v2
{
"tags": [
{
"name": "AreaA",
"tagType": "Folder",
"tags": [
{
"valueSource": "memory",
"name": "Name",
"value": 30,
"tagType": "AtomicTag"
},
{
"valueSource": "memory",
"name": "Donkey",
"value": 888,
"tagType": "AtomicTag"
},
{
"valueSource": "memory",
"name": "Location",
"value": 10,
"tagType": "AtomicTag"
}
]
},
{
"name": "AreaC",
"tagType": "Folder",
"tags": [
{
"valueSource": "memory",
"name": "Name",
"value": 35,
"tagType": "AtomicTag"
},
{
"valueSource": "memory",
"name": "Details",
"value": 1,
"tagType": "AtomicTag"
},
{
"valueSource": "memory",
"name": "Zoo",
"value": 200,
"tagType": "AtomicTag"
}
]
}
]
}