Easily determine changes to model between versions committed to repository for code reviews
0
Hello all, I teams server when new changes are committed to model, e.g. microflow or pages, etc, the version history only shows what documents were updated. But it doesnt show the actual diff, i.e. what was changed from prior version. And this is hard from code review perspective. Traditionally in source version system, we can do diff between versions to see the exact changes and this is very helpful. Is there a way to be able to do 'diff' to actually review changes committed?
asked
Alpa Parekh
1 answers
0
There is no easy way to identify it on team server. What our team currently doing is we are running a pipeline to utilise mx command tool to do a diff before merge request on gitlab. You may refer to Merging and Diffing Commands | Mendix Documentation to checkout this tool. It will generate diff in a json format. Although it's not perfect but it will be something auditable.