Chapters

13 Chapters | 1:03:27 |

01

Upgrading to Symfony 3.3!

5:21
02

_defaults, autowire & autoconfigure

5:20
03

Service Class Name as Service id

4:11
04

Making all Services Private

3:06
05

Auto-Registering All Services

5:24
06

Controllers as Services

2:06
07

Understanding Autowiring Logic

4:43
08

Problematic Multi-Class Services

5:05
09

Autowiring Controller Arguments

6:20
10

Aliases & When Autowiring Fails

3:46
11

Autowiring Deprecations

5:36
12

Configuring Specific (Named) Arguments

3:10
13

RAD with Symfony 3.3

9:19

> Symfony 3 > Symfony 3.3: Upgrade, Autowiring & Autoconfigure

Buy Access to Course

07.

Understanding Autowiring Logic

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $6.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or Register to check out the script

5 Comments

Sort By

Login or Register to join the conversation

Trafficmanagertech 8 years ago

I get this deprecation error: "Autowiring services based on the types they implement is deprecated since Symfony 3.3 and won't be supported in version 4.0. Try changing the type-hint for argument "$em" of method "AppBundle\Service\Settings::__construct()" to one of its parents: interface "Doctrine\ORM\EntityManagerInterface", or interface "Doctrine\Common\Persistence\ObjectManager"."

I don't understand, why I have to typehint the EntityManagerInterface and not the EntityManager?

|

toporovvv Trafficmanagertech 8 years ago

Because typehinting on interface has much more flexibility than on exact class. That allows you to change realisation of injected class without changing all the typehints where it's used.

1 |

MolloKhan SFCASTS Trafficmanagertech 8 years ago edited

Hey Trafficmanagertech

As far as I know that change was made to encourage programmers to depend upon interfaces instead of concrete classes

Have a nice day

|

boykodev MolloKhan 7 years ago

Nevermind, it was answered in episode 10 - https://symfonycasts.com/sc...

|

boykodev MolloKhan 7 years ago

But if there's two or more classes in the container, which implement that interface or extend that concrete class, autowiring won't work, right?

|

Symfony 3

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.5.9",
        "symfony/symfony": "3.3.0-RC1", // v3.3.0-RC1
        "doctrine/orm": "^2.5", // 2.7.5
        "doctrine/doctrine-bundle": "^1.6", // 1.10.3
        "doctrine/doctrine-cache-bundle": "^1.2", // 1.3.5
        "symfony/swiftmailer-bundle": "^2.3", // v2.6.7
        "symfony/monolog-bundle": "^3.1", // v3.2.0
        "symfony/polyfill-apcu": "^1.0", // v1.23.0
        "sensio/distribution-bundle": "^5.0", // v5.0.25
        "sensio/framework-extra-bundle": "^3.0.2", // v3.0.29
        "incenteev/composer-parameter-handler": "^2.0", // v2.1.4
        "composer/package-versions-deprecated": "^1.11", // 1.11.99.4
        "knplabs/knp-markdown-bundle": "^1.4", // 1.7.1
        "doctrine/doctrine-migrations-bundle": "^1.1", // v1.3.2
        "stof/doctrine-extensions-bundle": "^1.2" // v1.3.0
    },
    "require-dev": {
        "sensio/generator-bundle": "^3.0", // v3.1.7
        "symfony/phpunit-bridge": "^3.0", // v3.4.47
        "nelmio/alice": "^2.1", // v2.3.6
        "doctrine/doctrine-fixtures-bundle": "^2.3" // v2.4.1
    }
}

Previous Chapter

Next Chapter