callme | Phono add-on and jQuery plugin | Plugin library

It would appear that within my custom hook I can import Apollo Client, this then gives me the ability to use mutations and queries.

You are creating a new module layer containing two modules and establishing access of one of these modules to the other. However, you actually want to establishing access for the currently running main method to one the these modules.

The currently running main method can’t be part of the new module layer it just creates. Assuming standard launcher setup, it belongs to a Controller module loaded by the system class loader as part of the boot-layer.

So, instead of granting access to a new module of the same name in the new layer, you have to change the code to grant access to the already loaded Controller module. Since the new Controller module of the new module layer serves no purpose then, you can remove it from the layer configuration.

In general, injecting an IServiceProvider (or any abstraction that gives access to an unbound set of dependencies is a bad idea, because it can lead to the Service Locator anti-pattern. A discussion on this anti-pattern can be found here.

A Service Locator is something that only exists outside the Composition Root. Your BackgroundService1, however, might be part of the Composition Root, which might injecting a DI Container -or an abstraction there over- a feasible solution. Note that you should strive keeping all business logic out of the Composition Root. This ensures that BackgroundService1 purely functions as a mechanical peace of code that delegates the operation to classes that run the actual business logic.

Though, when operating inside the Composition Root, there is typically no need to use an abstraction over your DI Container, such as an IServiceProvider. The Composition Root already has intrinsic knowledge over all application's dependencies, including your DI Container.

This means that you can inject LightInject's ServiceContainer directly into the constructor of BackgroundService1; there is no need for an IServiceProvider.

If, however, you insist in using the IServiceProvider abstraction, you can create an IServiceProvider implementation that wraps ServiceContainer and forwards its GetService method to the wrapped ServiceContainer. This wrapper class can than be registered in the ServiceContainer.

You're actually using the rest syntax, which is how you let a function have an infinite number of arguments which will be presented as an array of arguments.

You need to put . for use selector class like:

You should return a String (or String? if you want, but it is not necessary in this case) from the User's callMe method:

Try the following code...

How to access the correct `this` inside a callback

If I understand correctly, what you are looking for is string interpolation. The syntax for this is #{...}, like so: