I am a bit baffled that I could not find another thread about this. Whenever a setting is changed on a component instance, it is treated as an override even if the value is the same as the main component. There is no easy way to keep track of those overrides, and it often leads to unneccessary mismatch between the main component and the instances. Some examples:
- I have a button component. The horizontal margin is 20px. At some point in my process, I want to see how it would look if I changed it to 10px on one of the instances. I later decide that 20px worked fine, so I change it back. Now, if the main button component is redesigned so that 16px is the standard value, the aforementioned instance will still stay 20px. The only way to restore this connection is to choose Reset-> All changes (because there is no specific reset for the margin). That will of course also reset the label of the button so I have to enter that again.
- I have an info card component with some text in it. The text is black in the main component. I do some testing in my local design and change the text to dark gray. That works well, and I decide to change to the same gray on the main component. Later, the gray color needs to be tweaked a bit. Because I forgot to reset the color of that first instance, it will now not update.
Similar cases has caused a lot trouble to me during the years. And it becomes even more complicated now with the variables/design tokens that can potentially reference the same value so there is no visual difference.
Please consider fixing this so that the setting is not seen as an override if the value is the exact same as in the main component.