Chapters

29 Chapters | 1:34:37 |

01

Introduction

1:00
02

ManyToOne Doctrine Relationships

4:40
03

Sharing Data between Fixture Classes

1:49
04

Restricting Edit Access to Owners

1:53
05

Using a shortcut Base Controller Class

2:30
06

Using PHPDoc for Auto-Completion

1:26
07

OneToMany: The Inverse Side of a Relationship

5:37
08

Doctrine Extensions: Sluggable and Timestampable

4:30
09

Using the slug in the Event URL

2:04
10

Adding createdAt and updatedAt Timestampable Fields

1:41
11

Creating a Custom orderBy Query

2:11
12

ManyToMany Relationship

2:37
13

Using the ManyToMany so Users can Attend an Event

4:53
14

More with ManyToMany: Avoiding Duplicates

2:51
15

JSON up in your Response

2:50
16

Come on, Set the Content-Type Header!

3:19
17

Adding the AJAX Touch: JavaScript

2:16
18

Customizing Error Pages and How Errors are Handled

6:01
19

Render another Controller in Twig

4:28
20

Creating a Pretty CSV Download

4:19
21

Your Very First Service

4:42
22

Symfony Overlord: The Service Container

4:58
23

Configuration Loading and Type-Hinting

2:01
24

Dependency Inject All the Things

3:14
25

Twig Extensions and Dependency Injection Tags

4:33
26

Doctrine is in your Lifecycle (with Callbacks)

2:08
27

Doctrine Event Listeners

5:59
28

Doctrine Listeners on Update

2:48
29

Keep Going!

1:19

This tutorial has a new version, check it out!

> Symfony 2 > Starting in Symfony2: Course 3 (2.4+)

Buy Access to Course

21.

Your Very First Service

|

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 $12.00

Previous Chapter

Next Chapter

Login or register to check out the script

11 Comments

Sort By

Login or Register to join the conversation

Eduardo Guglielmotti hace 8 años

In symfony 3 it does not work. Fails:
AutowiringFailedException

Cannot autowire service "AppBundle\Reporting\EventReportManager": argument "$em" of method "__construct()" must have a type-hint or be given a value explicitly.

|

MolloKhan SFCASTS Eduardo Guglielmotti hace 8 años edited

Hey Eduardo Guglielmotti

You are right, in order to use the "auto-wiring" service you have to type-hint your arguments, because the container needs to know which object has to inject.

Can you tell me in which chapter does it happens?

Cheers!

|

Eduardo Guglielmotti MolloKhan hace 8 años

I was trying it with symfony 3.3 following https://knpuniversity.com/s...

regards

|

MolloKhan SFCASTS Eduardo Guglielmotti hace 8 años

Thanks!
I hope you are enjoying our tutorials :)

Have a nice day

|

Eduardo Guglielmotti MolloKhan hace 8 años

Thank you
But I do not know what I've done wrong so it does not work, well in Symfony 3 it's different.

Do you have any idea of my mistake?

|

MolloKhan SFCASTS Eduardo Guglielmotti hace 8 años edited

You would only have to type-hint your argument, something like this:


use Doctrine\ORM\EntityManager
...
class ReportManager { 
    public function __construct(EntityManager $em) {
    ....
    }
    
    ....
}

Then, the container will do the rest. If you are not using Symfony 3.3, don't forget to register your service and activate the auto-wiring

|

MolloKhan SFCASTS hace 8 años

Hi there!

It's me again :D

I was wondering how can you inject services into Entity Repository.

I made a service for my user's entity in order to handle my custom ID generator and I would like to inject it to my repositories.

Thanks in advance :)

|

weaverryan SFCASTS MolloKhan hace 8 años

Hi Diego!

You *can* do this, but you shouldn't :). Basically, the repository should *only* have queries. If you're doing something in there that needs an additional service, then it's probably something that no longer belongs in the repository. For these things, I very commonly create "Managers" - e.g. PostManager (if Post is your entity). You can certainly have the PostManager call the PostRepository (just inject the entity manager, I do this all the time).

Hope that helps!

1 |

MolloKhan SFCASTS weaverryan hace 8 años

Nice, I'll go that way

Thx :)

|

Oscar Untied hace 8 años

Why do we split, the service from the controller? What can i see as the difference between a controller and a service now? That a controller can call a service multiple times depending on what the logic would tell the controller to do, and that the service only does work once for each call?

|

weaverryan SFCASTS Oscar Untied hace 8 años

Hi Oscar!

This is a question that strikes *right* at the heart of the purpose of services :). You could keep your life simple and code 100% in your controller. There are a few disadvantages to this:

1) If you have logic in your controller, it can't be re-used on other pages (i.e. other controllers). This is the *biggest* reason.
2) If you have 50 lines of code in your controller, I need to read them to understand what they're doing. But, if you move them into a separate class - perhaps ImageHelper - and in a method - perhaps createThumbnail() - it becomes a lot more obvious *what* those 50 lines do. Organizing into services starts to naturally organize and self-document your code. This subtle advantage is one of my favorite
3) If you like to unit test, you need to move code into a separate spot.

Moving code from your controller into a service helps with each of these. Does that help?

Cheers!

|

Symfony 2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.3.3",
        "symfony/symfony": "~2.4", // v2.4.2
        "doctrine/orm": "~2.2,>=2.2.3", // v2.4.2
        "doctrine/doctrine-bundle": "~1.2", // v1.2.0
        "twig/extensions": "~1.0", // v1.0.1
        "symfony/assetic-bundle": "~2.3", // v2.3.0
        "symfony/swiftmailer-bundle": "~2.3", // v2.3.5
        "symfony/monolog-bundle": "~2.4", // v2.5.0
        "sensio/distribution-bundle": "~2.3", // v2.3.4
        "sensio/framework-extra-bundle": "~3.0", // v3.0.0
        "sensio/generator-bundle": "~2.3", // v2.3.4
        "incenteev/composer-parameter-handler": "~2.0", // v2.1.0
        "doctrine/doctrine-fixtures-bundle": "~2.2.0", // v2.2.0
        "ircmaxell/password-compat": "~1.0.3", // 1.0.3
        "phpunit/phpunit": "~4.1", // 4.1.0
        "stof/doctrine-extensions-bundle": "~1.1.0" // v1.1.0
    }
}

Previous Chapter

Next Chapter