Preferred instance lists should dynamically update with published library updates

In File A I create 20 (arbitrary example) different components that have an icon instance property. File A has access to my Icon library (in another file).
So I add all icons as preferred values for my 20 instance props in File A.

Now I add some icons to my library and publish the update. Well guess what? Now I have to go through the 20 props in File A to manually add those new icons as preferred value.

Imagine this at the scale of a mature international design system. What’s the point of the preferred values feature then?

2 Likes

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

Example: In File A we have ~100 different icons each as its own component.
File A acts as asset library for other files like File B where all our other components (atoms, molecules, organisms) lay. File B is connected with File A as it consumes their icons.

Now we want to add all the icons as preferred values for multiple components in File B.
Therefore we use the “select all” option.

Issue: Whenever we add additional icons to our library we have to go through all the props in File B again to manually add these new icons as preferred value. That’s because the selection of preffered values is static and does not automatically include the whole folder with all its components added afterwards.

At the scale of a mature international design system I assume this would happen automatically to reduce our effort as design system administrators. By that it’s really difficult to keep the preffered values updated.

There already was this feature request which unfortunately got closed:
Preferred instance lists should dynamically update with published library updates)

@Dennis_N Hey! I went ahead and re-opened the old topic you mentioned, and merged it with yours. That way we could keep track of +1s in one place :smiley:

Thank you for the request/feedback.

2 Likes