Nested components and configuration propagation

[kienerj]

In essence this thread:

Feature request: propagate configuration nodes of nested components

I’m trying to make a number of reusable components using R scripts. They produce text, a table or a plot which all are nicely propagated to the highest level. Super! When a lower level component requires a configuration node this unfortunately isn’t propagated to a higher level (see older issue on this forum). The work-around suggested to copy those configuration nodes to the higher level components and pass the parameters via flow variables, makes those lower level components less reusable. …

Is it possible to propagate configuration nodes to higher levels like this is done for output in the Interactive Output?

And then KNIME response:

thanks for your feedback. This is a request that comes up more and more often, so we’ve filed a feature request for that. Will keep you posted.

This is now 5 years old. What is the status? It would still be very helpful to have on a component level the option to propagate config up or not. I have complex components with > 10 config options and having to copy paste them all together into a big mess at the top level just doesn’t really seems useful or clean.