Hello NogaS. I don't have an answer for you but maybe something to consider as a work around... I notice the use of project properties for some of the fields. Could you have a project property (or suite, or testcase property) defined for that field that is empty. At least saving would not remove it since there would be content there henceforth.
Your question piqued my curiosity on the GIT topic because the team i am on is just embarking on composite projects workflow in GIT with multiple people working on a project.
Hi
Thank you for your comment and sorry for the late response. The properties are already there at the beginning, this is why the ReadyAPI behavior is surprising. Our R&D manager took over the case with ReadyAPI and they suggest a fix should be in place in Q2 or Q3 this year (2021).
In the meantime, a co-worker suggested this - https://community.smartbear.com/t5/API-Functional-Security-Testing/How-do-I-minimize-merge-conflicts-in-a-ReadyApi-composite/m-p/141226/highlight/true#M31751
Looks good but I didn't try it. Our current practice is, unfortunately, not to work on the same project at the same time.
Regards,
Noga
