Chapters

11 Chapters | 1:02:30 |

01

Interrupt Symfony with an Event Subscriber

8:40
02

HttpKernel::handle() The Heart of Everything

5:46
03

kernel.request and the RouterListener

9:48
04

Finding and Instantiating the Controller

6:42
05

kernel.controller Event & Controller Arguments

5:54
06

The kernel.view Event

3:17
07

Finishing with kernel.response and kernel.exception

5:34
08

Symfony Magic: Replace the _controller

2:23
09

Making an Argument Available to All Controllers

3:57
10

What about Sub Requests?

4:31
11

How Sub-Requests Work

5:58

This tutorial has a new version, check it out!

> Symfony 3 > Journey to the Center of Symfony: HttpKernel Request-Response

Buy Access to Course

04.

Finding and Instantiating the Controller

|

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

Previous Chapter

Next Chapter

Login or register to check out the script

3 Comments

Sort By

Login or Register to join the conversation

s.molinari 8 years ago

Hi Ryan,

Being the n00b I am to Symfony and also being the curious person I am, I went in even deeper and looked at this,

$controller = $this->parser->parse($controller);

because I didn't and still don't understand why "Action" is added to the defined function name for the controller, when using routing.yml or routing_dev.yml.

Can you explain why this is done and necessary? Is there a logical reason or is it just something Symfony imposes, as a sort of best practice? Because, I was totally confused at first. I was like, why do I need to name my function "indexAction" or "showAction" in the controller, when it is called "index" and "show" in the routing parameters. And, this little minor "strangeness" is never explained in the docs.

Scott

|

weaverryan SFCASTS s.molinari 8 years ago edited

Hey Scott!

Nice digging :). Yes, it's just a convention that's "imposed" on you - the idea being that it helps keep your method names consistent. In reality - whether it's a good idea or not - it causes the exact confusion you're mentioning for beginners - it's a Symfony-ism to learn. That's one of (but not the only) reason why I now recommend using annotation routes.

As a side-note, now that you've been through this, you'll notice that, if you really want to, you can avoid this convention simply by putting the full class :: method name in your routing.yml:


my_page:
    path: /dinosaurs
    defaults:
        _controller: AppBundle\Controller\DefaultController::indexAction

It's not, that's why it's not too practical. But because of this format, you don't go into the if block that uses the parser - because you're already in the "final" format. You can safely remove the "Action" suffix here if you wanted to and it would work fine.

Cheers!

|

s.molinari weaverryan 8 years ago

Thanks Ryan.

I think as I run into these "Symfony-isms" I'll jot them down and maybe make my own blog post about them.:)

Scott

|

Symfony 2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.3.3",
        "symfony/symfony": "2.6.x-dev", // 2.6.x-dev
        "doctrine/orm": "~2.2,>=2.2.3", // v2.4.6
        "doctrine/doctrine-bundle": "~1.2", // v1.2.0
        "twig/extensions": "~1.0", // v1.2.0
        "symfony/assetic-bundle": "~2.3", // v2.5.0
        "symfony/swiftmailer-bundle": "~2.3", // v2.3.7
        "symfony/monolog-bundle": "~2.4", // v2.6.1
        "sensio/distribution-bundle": "~3.0", // v3.0.9
        "sensio/framework-extra-bundle": "~3.0", // v3.0.3
        "incenteev/composer-parameter-handler": "~2.0", // v2.1.0
        "hautelook/alice-bundle": "~0.2" // 0.2
    },
    "require-dev": {
        "sensio/generator-bundle": "~2.3" // v2.4.0
    }
}

Previous Chapter

Next Chapter