Comments
Sort by recent activity
Yes it does. I'll see how it works but editing the XML isn't an issue. Thank you. / comments
Yes it does. I'll see how it works but editing the XML isn't an issue. Thank you.
Rescan adds missing ones but doesn't to remove those that are not used anymore and that don't exist anymore.
Yes it affects greatly merges but also change tracking/code review. When you had something using default attributes values and then it gets changed to something with attributes explicitly defined, you don't know if those changes change anything and what they change.
Exanpe:
- <Foo />
+ <Foo Bar="1" />
Does it mean the "Bar" is now enabled and wasn't before? What affect does "Bar" mean anyway? / comments
Rescan adds missing ones but doesn't to remove those that are not used anymore and that don't exist anymore.
Yes it affects greatly merges but also change tracking/code review. When you had somethi...
Ideally the SA project editor should have 3 states for such. One being the default, the rest being the defined value. This is only supposing that you wish to possibly change the default value later on. If the default value stay for backward compatibility then better never include the default value. This would be clear.
I forgot to specify that the hardest part in regards to source control systems, is that when merging or doing changes it's impossible to know if those values mean the same as not specifying any. This is because there is no reference XML documentation for it. / comments
Ideally the SA project editor should have 3 states for such. One being the default, the rest being the defined value. This is only supposing that you wish to possibly change the default value later...