kylerc
Well-known member
As an idea, would it be possible for the hashes to be stored in a separate file outside the _metadata.json (perhaps _hashes.json) when development mode is enabled so that file could be ignored by version control? Our team uses git to version UI.X, but we constantly have merge conflicts since hashes are changing all the time for templates. We don't have the option of ignoring _metadata.json since other information is stored there that we need to retain (version ids). I recognize that moving to a separate file takes up a bit more space and might have performance implications, but if this was only in development mode, I feel like that would be well worth it for clean version control.
Upvote
0
