Is the Instantiator class in Flow considered a public API? In a sense that can I use it to improve the DX of add-ons 
I found a documentation page for it, but that pretty much just discusses customizing its implementation, not about its usage. The Javadocs only discusses framework internal usage.
With many add-ons, DI framework support could improve the DX. Like with a map component, configuration of the background layers could be delegated to some bean (kind of a cross cutting concern), . I have been tempted to use Spring dependency in some add-ons, but I wouldn’t like to close the door for CDI or plain Java users.
I quickly tested that something like this seems to work at least with SB project, but I have no idea if I can trust it works in the next version :
public interface Jorma {
String getMyConfig();
}
@Component
public class JormaImpl implements Jorma {
@Override
public String getMyConfig() {
return "It works!?";
}
}
@Route
public static class MainView extends VerticalLayout {
public MainView() {
// Add-on would use Jorma like this:
Jorma bean = VaadinService.getCurrent().getInstantiator().getOrCreate(Jorma.class);
// if not available, use some default config
String myConfig = bean.getMyConfig();
}
}
I’ll make a PoC to the Maplibre add-on. I’d guess only the getOrCreate or createComponent methods would be relevant for any add-ons. I wonder how framework is using the latter 
