How to inject dependencies into a plugin? Or what is the best practice for a work around?

[sundeepgupta]

I'm looking at building an iOS plugin, although my question applies to Android as well. What I've noticed is that the plugin is initialized directly by the bridge. And obviously plugin function calls are also made by the bridge. So, it doesn't seem possible to use constructor or parameter injection. Is this correct? If so, I can see a couple of work arounds, but wanted to first make sure I'm not missing something.

[ikeith]

Correct. There is no scheme to handle injection for you. The plugin is expected to manage its own dependencies. The bridge will call the load method on each plugin after it is instantiated and before it receives any calls from the application. So that is where it should configure anything that it will need later.

[sundeepgupta]

Understood - thanks. It would be great, perhaps for future consideration, if initialization could be (optionally) controlled by the native code to allow for constructor injection.

[mlostekk]

A DI mechanism is definitely required for serious usage of capacitor, like the "ModuleFactory" approach in React Native.

Nobody wants to handle god objects.