Feature RequestsFeature requests, product enhancement ideas, and other product-specific suggestions.
Make diff's of .psf files useful
ALIENQuake, Jun. 29, 2019Under Review
Every time when I modify a form, there is a huge change of 'xml data' part inside file. Same thing when I replace resource image with another.
The diff's are huge and it's very uncomfortable to see actual code changes. I'm aware that this is because of psf merge some code + data.
Spliting psf files into two:
- one with actual code
- one with xml data
would be easiest solution.
Comment by brittneyr, Sep. 19, 2019
Psf files are form projects and contain all the information for the designer. Have you tried exporting the forms to ps1 script files before comparing?
Comment by ALIENQuake, Oct. 2, 2019
The "psf" files also contains my custom code for the application. If the custom code (and only code) associated with form would endup inside separate file, it wont be a problem. Spliting psf file into two shouldn't be a problem, espacially when you consider 'exe' distribution.
Are you suggesting that I should export all "psf" files as ps1, commit those extra ps1 files into git and then, after every single change of "psf" repeat this process so I could look at the differences of exported ps1 files and not actuall "psf" files? I'm sorry but I don't accept you suggestion as valid.
Very important advantage of using source control is to see changes between two commits. The current "psf" design" prevents it. I'm sure that putting all into "psf" files was done for some reasons. But if the outcome prevents seeing changes between two commits, it's very big drawback. It prevents code cooperation and rewiews. Just image how "psf" diffs would look inside email messages.
Please rethink the current "psf" design.