@jbpasquier I would also say that changing the attribute on the widget, if possible, would be better in terms of performances. If you change it on the component, you need to re-render it entirely
@manonbou tested and attaching a MutationObserver to a component to re-render it as soon as an attribute change seems to cause a lot of problems. We have a lot of additional renders and it means detaching widgets from the DOM to create new one, which seems very bad in terms of performances
I'm not sure I understood your point. What I was saying is, instead of changing the label-field attribute on the component, you can change the label attribute on the widget directly. But this won't duplicate anything.