# Dependency Injection

## Introduction

doMynation uses [dependency injection](https://en.wikipedia.org/wiki/Dependency_injection) to wire dependencies across the framework.

### Container-Aware Entities

Below is the list of classes and methods supplied by the framework that are aware of the dependency injection container, which means they can be injected dependencies via constructor arguments or function/method arguments:

* The `Module::boot()` method
* Closures of [simple routes](https://domynation.gitbook.io/domynation-framework/routing-1#simple-routes)
* Constructor of [Actions](https://domynation.gitbook.io/domynation-framework/routing-1#actions) and their optional `validate()` method
* Constructor of `RouteMiddleware`

### Core Dependencies

The framework registers and makes the following dependencies available in any container-aware entity:

| Class/Interface            | Description                                                      |
| -------------------------- | ---------------------------------------------------------------- |
| `Request`                  | The current request.                                             |
| `RouterInterface`          | The framework's router to register routes.                       |
| `ViewFactoryInterface`     | The utility for loading templates/views and register namespaces. |
| `CommandBusInterface`      | The command bus.                                                 |
| `UserInterface`            | The currently logged-in user (if any).                           |
| `EntityManager`            | Doctrine's ORM.                                                  |
| `CacheInterface`           | The utility to store and retrieve data from the cache.           |
| `StorageInterface`         | The utility to store files.                                      |
| `MailerInterface`          | The utility to send emails.                                      |
| `EventDispatcherInterface` | The event dispatcher, to fire and listen for events.             |