The version history in DTM for published containers is great but I'd love to see DTM Launch have Version Control for code changes when you "save" a rule without publishing the container.
Can you explain a little bit more exactly what you mean? Every time you save custom code in a code editor, you'd want there to be a version history for that specific code block? Maybe the ability to look at previously saved versions and revert to one? Just trying to understand how you'd envision this working.
The ability to look at previously saved versions of the custom code in the code editor and revert to one (maybe create a separate button and call it "save version")
We have multiple people creating rules in our DTM and we encounter problems where the other would override the code of the other if they're both editing the same rule.
Are you referring to this...? If so that would be GREAT!
Kindof but more like just saving the version of the code without the container getting published first before you see the history
GitHub integration would be phenomenal.
We would love:
1. the ability to search across tags,
2. the ability to see change history per line of code,
3. the ability to review code.
I think every dev environnment/librairy needs to have its own version of its rules, data elements and extensions from the published version forward. Making an analogy to github, every environnment is a different branch, and published is the master. Or, like google tag manager and workspaces...