PHP-DI | The dependency injection container for humans | Dependency Injection library

I got it working by using send_long_data method. (in these examples I have removed some irrelevant columns for the example).

The benefit of using b according to https://www.php.net/manual/en/mysqli-stmt.bind-param.php:

Note:

If data size of a variable exceeds max. allowed packet size (max_allowed_packet), you have to specify b in types and use mysqli_stmt_send_long_data() to send the data in packets.

To autowire the dependencies, you have to use the DI container.

Example:

What you placed at the top of your PHP.INI file is what you would use in an actual .php file to turn on error reporting / show errors on a per file bases. You do not add that to your PHP.INI file.

Example of use in a .php file:

Enabling gRPC PHP extension seems to fix the problem:

The solution, as given by @CertainPerformance, is a trivial variation on the linked solutions given elsewhere.

Echoing back the following allows for appending to the DOM as expected:

As pointed by Nima with the tickets, Circular Dependencies can't be solved using setter, unless you use Lazy Loading. The catch is that it requires a proxy libs, that have 3 additional dependencies, which is a bit overkill for my simple use case. (also it seems that there's a missing step in the documentation of PHP-DI)

• zendframework/zend-eventmanager (3.2.1)
• zendframework/zend-code (3.4.1)
• ocramius/proxy-manager (2.2.3)
• ocramius/package-versions (1.5.1)

To workaround this, I manually did the job of PHP-DI.

• I set a setter on my Logger to set the SlackService, once the container is built, and I did not add the @Inject in the comments above the setter method.

You could create a mocked repository and set it into the container. The rest will be resolved via autowiring. Make sure that your container is getting reloaded for each test.

Example

To set a mocked instance into the container add this method into a trait or base class:

First, you are using dependency and container terms as if they are the same thing, which they are not.

About the problem with your code, in Flash::register() method, you are creating a new object from Messages class and putting this in the DI container. You are calling this method and forcing creation of the Message object, which needs the session to be already started, before letting the middleware start the session. You really should avoid storing objects in DIC, instead of storing their definition (how they are built). The following change is what I mean:

I suggest using two different objects of MyMiddleware class for different groups, each constructed using appropriate implementation of IMyInterface. You can tell PHP-DI to call the constructor with the parameters you want.

Here I created two instances of MyMiddleware, one with the name AdminMiddleware and the other named ApiMiddleware in the container. using DI\create()->constructor() method, I configure the DI to inject different implementations of IMyInterface while building these two objects: