How do you track changes in UDT.json with GitHub?

Ignition
1

Hi everyone,

I'm trying to track changes for UDT.json files in GitHub.

I've noticed that each time I export a UDT to JSON, the file structure and property ordering can change, even when there are only minor modifications. As a result, GitHub shows a large number of differences, making it difficult to review changes line by line and identify the actual modifications.

Has anyone successfully used GitHub to track UDT changes across versions?

If so:

  • Do you use any tools or scripts to normalize/sort the JSON before committing?
  • Is there a recommended export format or workflow?
  • How do you review changes efficiently between UDT versions?

Any tips or best practices would be greatly appreciated.

Thanks!

2

Hello,

I would recommend using:

It worked well for when I was still on 8.1. Docs aren't on the current repo but it seems like the archived repo has the docs deployed. If I remember correctly, individualFiles is the best configuration if you want to reduce conflicts for the udts.

On 8.3, udt definitions are stored (albeit wonky IMO) in tag-type-definition. See my post here about my current challenges if you are curious.

3

Thanks for the recommendation and the additional details. I'll check it out!