Changes to component descriptions should not cascade component updates

Publishing updates to component descriptions should not force updates everywhere that component is used, triggering cascading updates for everything in the design system.

I manage the design system for my company and having to explain to every other designer on the team “no it’s ok, there are no updates to the actual component itself, please just accept the update” whenever I add descriptions to a component (e.g. adding alternate names to icons for easier lookup) is frankly a huge waste of my time. Designers on the team frequently will not accept an update for its description and I’ll discover weeks or months later that they are using outdated versions of the components as they learn to continuously ignore the component update alert.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.