Chapters

18 Chapters | 1:50:35 |

01

Creating a new Symfony 5 Project

6:05
02

Meet our Tiny App + PhpStorm Setup

5:30
03

Route, Controllers & Responses!

5:56
04

Annotation & Wildcard Routes

6:10
05

The Lovely bin/console Tool

2:42
06

Flex, Recipes & Aliases

6:26
07

How Recipes Work

3:06
08

The Twig Recipe

3:46
09

Twig ❤️

10:14
10

Profiler: Your Debugging Best Friend

6:46
11

Assets: CSS, Images, etc

9:58
12

Generate URLs

5:11
13

JSON API Endpoint

6:29
14

JavaScript, AJAX & the Profiler

7:12
15

Smart Routes: POST-only & Validate {Wildcards}

4:04
16

Service Objects

8:25
17

Hello Webpack Encore

4:05
18

Webpack Encore: JavaScript Greatness

8:30

This tutorial has a new version, check it out!

> Symfony 5 > Charming Development in Symfony 5

Buy Access to Course

16.

Service Objects

|

|

Autoplay

Previous Challenge

Next Challenge

Login or register to check out the script

5 Comments

Sort By

Login or Register to join the conversation

Boran Alsaleh 5 years ago

Hi when we send a request to our Controller for example index(LoggerInterface $logger) , does symfony create a new logger object at this moment and inject it to the controller or is this object already created before “e.g in kernel “and just we are using an existing object from symfony behind the seen could you please explain me that & how symfony is creating this obj inject it into our . Thanks in Advance

1 |

Victor SFCASTS Boran Alsaleh 5 years ago

Hey Boran,

Good question! All the autowiring things are related to Symfony's Dependency Injection Container. That container knows everything about creating those objects, i.e. how to create that Logger object, etc. So the container is responsible for the creation of them. And yes, if we're talking about LoggerInterface - it will either created a new instance of it if it has not been created yet, or just will pass the instance that was already created before. For example, if you have an event listener that is called earlier than that controller, and that listener also requires the same LoggerInterface object - the same object will be passed to the controller. But if no code requires the logger before the controller - a new instance will be created and passed.

In shorts, learn more about Symfony's Dependency Injection and Dependency Injection Container to know more about how it works.

I hope this helps!

Cheers!

1 |

Peter-K 5 years ago

We had to inject loggerinterface but we are not injecting environment. Why is it coded this way? Both objects are services but one of them is not injected. Why accessing approach is not consistent? In other words why it is not designed that way that I can just type $this->info(). There seems to be more of them.

'router' => '?'.RouterInterface::class,
'request_stack' => '?'.RequestStack::class,
'http_kernel' => '?'.HttpKernelInterface::class,
'serializer' => '?'.SerializerInterface::class,
'session' => '?'.SessionInterface::class,
'security.authorization_checker' => '?'.AuthorizationCheckerInterface::class,
'twig' => '?'.Environment::class,
'doctrine' => '?'.ManagerRegistry::class,
'form.factory' => '?'.FormFactoryInterface::class,
'security.token_storage' => '?'.TokenStorageInterface::class,
'security.csrf.token_manager' => '?'.CsrfTokenManagerInterface::class,
'parameter_bag' => '?'.ContainerBagInterface::class,
'message_bus' => '?'.MessageBusInterface::class,
'messenger.default_bus' => '?'.MessageBusInterface::class,

Why one of them is not logger => '?'.LoggerInterface::class?

|

Victor SFCASTS Peter-K 5 years ago

Hey Peter,

Those are just different approaches that allow you to achieve same results. Controllers are special, and allow you to use method injection instead of constructor injection - this gives you some more flexibility as on the request only those services will be booted (created) that are used directly in the specific controller's action. If you would use construction injection - most probably it would mean that you would use only some of those methods in a specific action, and some other in another specific action... but they all will be booted in the constructor no matter what action is hit. So in some cases it makes sense to use constructor injection when you want to share services across the whole class, and in some cases - use method injection to share some services across the specific method only, i.e. make them to be booted and available in a specific method only.

Anyway, you can choose whatever method you like more, or whatever you're comfortable with - we just try to show you all possible options you have in our tutorials ;)

Cheers!

|

This tutorial also works great for Symfony 6!

Symfony 5.0

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.3.0 || ^8.0.0",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "easycorp/easy-log-handler": "^1.0.7", // v1.0.9
        "sensio/framework-extra-bundle": "^6.0", // v6.2.1
        "symfony/asset": "5.0.*", // v5.0.11
        "symfony/console": "5.0.*", // v5.0.11
        "symfony/debug-bundle": "5.0.*", // v5.0.11
        "symfony/dotenv": "5.0.*", // v5.0.11
        "symfony/flex": "^1.3.1", // v1.21.6
        "symfony/framework-bundle": "5.0.*", // v5.0.11
        "symfony/monolog-bundle": "^3.0", // v3.5.0
        "symfony/profiler-pack": "*", // v1.0.5
        "symfony/routing": "5.1.*", // v5.1.11
        "symfony/twig-pack": "^1.0", // v1.0.1
        "symfony/var-dumper": "5.0.*", // v5.0.11
        "symfony/webpack-encore-bundle": "^1.7", // v1.8.0
        "symfony/yaml": "5.0.*" // v5.0.11
    },
    "require-dev": {
        "symfony/profiler-pack": "^1.0" // v1.0.5
    }
}

Previous Challenge

Next Challenge