This is really nasty when working in a bigger project with git it means to go through several submodules and undo commits and not have a clear direct overview what you have actually changed. The extra minutes with every commit really sum up to quiet sum time, I got that it might not be an easy fix, but please give this some priority if possible.
2 Likes
This is really one off the most annayoing thing I am confronted with right now would be cool if you could consider to solve it
2 Likes
Latest preview addresses this issue by preserving the save state of the document (represented by the star on a document) when the system applies modifications to it. Up to now the save state was only preserved for modifications done by our converters (node and pin renamings). It didn’t apply for changes done on symbol level, like re-ordering pins on application side should the pins have been re-ordered on definition side.
Note that this will lead to a slightly different patching experience when for example changing the pin order in B. While B.vl will show up as modified, A.vl (using B) will not, even though when looking at A the pins are re-ordered accordingly. So even though A.vl will not show up as modified it will show changes on disk when explicitly saving it.
1 Like
Amazing works like charm thank you very much