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?

Kind regards,

Jan