diffing otherwise identical projects across ’source’ and ‘destination’ gateways always results in restructured (but functionally identical) resource.json files.
curious generally why this happens/if it will stop in 8.3, but not really a big deal..
except if designer saves will re-reorganize the structure again (untested as of this moment)
Is it all resource types, or resources of a particular type?
It sounds like an incidental bug in the way the JSON is being encoded; might or might not be incidentally fixed in 8.3 but I don't know if anyone has intentionally fixed it.
so far it’s “everything” except named queries - presuamably because there’s a lot more stuff in those so perhaps a different algorithm?
aaand it appears modifying the resource in designer does restructure the file again 
I’m moving a ‘local’ repo from the previous ‘dev’ gateway to a new gateway that has identical projects copied via EAM. Went ahead and committed all the modified resource.json files on a whim, thinking that was the ’right’ way/something had changed between version upgrades/whatever - nope.
also fun fact - it appears manual project exports (from gateway webpage anyway) don’t include empty folders
so lesson learned - copy the entire project(s) file structure over, not just the .git folder. I had opted for EAM in the first place to preempt any potential file system permission issues but clearly it’s not ideal.
