How to prevent ReadyAPI from randomly changing how it stores empty XML elements?
Why does ReadyAPI change how it stores a blank XML tag from, say <con:properties/> to <con:properties></con:properties> If I make one change and save, I may see many of these differences, which complicates review of the code. I see this in projects where Composite project is false, and in projects where it is true. The representation of blank XML elements is one of many things about how ReadyAPI stores a project that seem to change at random with each new version or sometimes randomly within the same version. I have tried setting the flag "Pretty prints project files", but this is not sufficient to stop this noise. Is there some other flag I can set so that the method for encoding the project doesn't obscure actual logic changes when I look at the differences? Preferably something that gets remembered in the project, rather than depending on a user setting? References: The following are a few postings that seem relevant, but don't clean up the random XML representations. "Version control - Diff is very confusing for ReadyAPI projects?" https://community.smartbear.com/t5/API-Functional-Security-Testing/Version-control-Diff-is-very-confusing-for-ReadyAPI-projects/m-p/209420#M47734 - Answer: Yes, currently, if you change one thing in ReadyAPI, several things in different places of the project might change as well. "How do I minimize merge conflicts in a ReadyApi composite project when working as part of a team?"https://community.smartbear.com/t5/API-Functional-Security-Testing/How-do-I-minimize-merge-conflicts-in-a-ReadyApi-composite/m-p/141151 - No accepted answer - Recommendation to check the flag "Pretty prints project files" "While this allows you to see exactly what has changed when diff-ing versions, it does have the problem that this is an application setting, thus you have to make sure all users set this value manually on their copies of ReadyAPI (If a user does not set this in their copy ReadyAPI it will revert to saving on a single line). Ideally I would like to see this as a project setting."Solved1.7KViews0likes7Commentsdiff capability for KiCAD schematics
I work for a company that focuses on electronics design. We do hundreds of schematic reviews and board layout reviews every month. Currently, we get a PDF of our schematic and review it in collaborator; which works fine. However, an ultimate feature would be if collaborator natively understood KiCAD file formats. KiCAD is a premier, open source, electronics design suite and the schematic files are plain text and designed to work with git. If you could consume kicad files and diff them for us; that would open up an entire new market for you.969Views0likes1CommentDiff capability for KiCAD PCB Layout files
I work for a company that focuses on electronics design. We do hundreds of schematic reviews and board layout reviews every month. Currently, we do not have a way of reviewing board layout, except having someone open up the editing software and stepping through the design. However, an ultimate feature would be if collaborator natively understood KiCAD file formats. KiCAD is a premier, open source, electronics design suite and the PCB files are plain text and designed to work with git. If you could consume kicad files and diff them for us; that would open up an entire new market for you.986Views0likes1Comment