The situation is the following.
We have an atomic design system. The most problematic ones are the buttons and inputs in this very extensive SaaS product we work on. The buttons and inputs have been replicated lots of times.
Since we have used atomic design approach we have nested component for the content, state, and size. Since the Properties update, nesting more than 2 levels starts to work badly, but again, we have replicated those components hundreds and hundreds of times, so we don’t really have a global view on how many overrides we have to take care of… creating those properties layers in the parent component will lead to a disaster.
What do we do update those very important elements?
And is it even on the table passing properties from a nested component to a parent one?
Thank you.
