Chapters

26 Chapters | 2:53:08 |

01

Events, Events & Events!

5:10
02

Hooking into Symfony with an Event Subscriber

5:54
03

index.php to HttpKernel::handle()

6:50
04

RequestEvent & RouterListener

6:26
05

Routing Secrets & Request Attributes

7:47
06

The Controller Resolver

7:03
07

Who Creates the Controller & Gives it the Container?

8:04
08

How does the Controller Access the Container?

4:14
09

The Argument Resolver

8:13
10

Argument Value Resolvers

5:32
11

How Service Autowiring Works in a Controller Method

7:36
12

Calling the Controller & View Event

5:20
13

kernel.response Event & Request Format

6:36
14

Finishing the Request

6:03
15

Exception Handling

9:29
16

The Critical kernel.exception Event Listeners

7:07
17

FlattenException & Error Status Codes

6:10
18

Serializer Error Renderer: JSON/XML Errors

5:40
19

How the HTML Error Page is Rendered

7:34
20

The Magic `_controller` Attribute

6:36
21

Custom Global Controller Arguments

5:37
22

How Entity Controller Arguments Work

4:54
23

Sub Requests

7:54
24

Sub Requests & Request Data

5:40
25

Manually Making a Sub Request

6:34
26

Sub Request Attributes

9:05

> Symfony 5 > Symfony 5 Deep Dive! The HttpKernel Request-Response Flow

Buy Access to Course

03.

index.php to HttpKernel::handle()

|

Autoplay

Previous Chapter

Next Chapter

Login or register to check out the script

7 Comments

Sort By

Login or Register to join the conversation

Jonathan_E 3 years ago edited

Hey @weaverryan and Team!

I've been diving deeeep into Symfony trying to load in some params from a 3rd party via an API request and then set these params at run time. I tried an onKernelRequest Subscriber and had the API request working etc, but... can't set the params here due to "Impossible to call set() on a frozen ParameterBag." error. So then I created a CompilarPass() class to try and get the params and set them during the container build process. But I run into a dependency injection loop where I need the RequestStack and my other FetchParams service in my CustomCompilarPass class but they aren't "built" in the container yet? So when I instantiate my CustomCompilarPass() in the kernel I actually need to inject my FetchParams service & RequestStack. I tried registering everything as services but I don't think they are available yet? Anyhow, just wondering if you had any advice on what to tap into to make an api request and set / modify some params at runtime. I know env file or environment variables are probably preferred but have an interesting use case. Thanks! Jon

|

MolloKhan SFCASTS Jonathan_E 3 years ago edited

Hey @Jonathan_E

That sounds interesting! I believe a compiler pass won't work because it is executed only once when Symfony boots the container. I think you can go with an event subscriber but implement a custom ParameterBag, but the problem will be where to store the data. I think you can use cache, the session, or a database. I hope it helps

Cheers!

|

Jonathan_E MolloKhan 3 years ago

Hey @MolloKhan!

Thank you for the suggestion. I'll give it a try and see how it turns out. It is sort of an odd scenario but looking forward to giving it a try. Take care! Jon

|

Cameron 4 years ago

I don't undertand the purpose of learning internals. ok, maybe I'll be able to contribute to the source coude or do some unusual hack to the core code, but I really don't understand what other (practical) reason a dev needs to know about the internals or even who this type of course is suited to. can someone help me out?

|

MolloKhan SFCASTS Cameron 4 years ago

In addition to what Ryan said, I find useful analyzing how Symfony is written and how it solve problems. Symfony puts extra effort on following good programming techniques and even applying design patterns, so, by reviewing how it works internally you don't only learn how it works, you also learn how to develop good OO code. Cheers!

2 |

weaverryan SFCASTS Cameron 4 years ago edited

Hey Fox C.!

That's a fair question. I think there is a portion of developers (I'd be guessing at the percentage) that just *like* to dive into the internals and know how the machine works. About the benefit of doing so? It's difficult to give specific examples, but the more you know of the internals, the more likely it is that if you hit a difficult issue, you'll have the knowledge to be able to jump into the core code and discover the solution for yourself. It's definitely not a requirement... and it takes serious time to learn the internals. If it's not your thing, I wouldn't worry about it - stick to the practical stuff.

Cheers!

2 |

Cameron weaverryan 4 years ago

Ok, so it's part knowing how to track down difficult issues too, thanks.

|

This tutorial also works well for Symfony 6!

Symfony 5

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.2",
        "ext-iconv": "*",
        "antishov/doctrine-extensions-bundle": "^1.4", // v1.4.3
        "aws/aws-sdk-php": "^3.87", // 3.133.20
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // 1.12.1
        "doctrine/doctrine-bundle": "^2.0", // 2.2.3
        "doctrine/doctrine-migrations-bundle": "^1.3|^2.0", // 2.2.2
        "doctrine/orm": "^2.5.11", // 2.8.2
        "easycorp/easy-log-handler": "^1.0", // v1.0.9
        "http-interop/http-factory-guzzle": "^1.0", // 1.0.0
        "knplabs/knp-markdown-bundle": "^1.7", // 1.9.0
        "knplabs/knp-paginator-bundle": "^5.0", // v5.4.2
        "knplabs/knp-snappy-bundle": "^1.6", // v1.7.1
        "knplabs/knp-time-bundle": "^1.8", // v1.16.0
        "league/flysystem-aws-s3-v3": "^1.0", // 1.0.24
        "league/flysystem-cached-adapter": "^1.0", // 1.0.9
        "league/html-to-markdown": "^4.8", // 4.9.1
        "liip/imagine-bundle": "^2.1", // 2.5.0
        "oneup/flysystem-bundle": "^3.0", // 3.7.0
        "php-http/guzzle6-adapter": "^2.0", // v2.0.2
        "phpdocumentor/reflection-docblock": "^5.2", // 5.2.2
        "sensio/framework-extra-bundle": "^5.1", // v5.6.1
        "symfony/asset": "5.0.*", // v5.0.11
        "symfony/console": "5.0.*", // v5.0.11
        "symfony/dotenv": "5.0.*", // v5.0.11
        "symfony/flex": "^1.9", // v1.21.6
        "symfony/form": "5.0.*", // v5.0.11
        "symfony/framework-bundle": "5.0.*", // v5.0.11
        "symfony/mailer": "5.0.*", // v5.0.11
        "symfony/messenger": "5.0.*", // v5.0.11
        "symfony/monolog-bundle": "^3.5", // v3.6.0
        "symfony/property-access": "5.0.*|| 5.1.*", // v5.1.11
        "symfony/property-info": "5.0.*|| 5.1.*", // v5.1.10
        "symfony/routing": "5.1.*", // v5.1.11
        "symfony/security-bundle": "5.0.*", // v5.0.11
        "symfony/sendgrid-mailer": "5.0.*", // v5.0.11
        "symfony/serializer": "5.0.*|| 5.1.*", // v5.1.10
        "symfony/twig-bundle": "5.0.*", // v5.0.11
        "symfony/validator": "5.0.*", // v5.0.11
        "symfony/webpack-encore-bundle": "^1.4", // v1.11.1
        "symfony/yaml": "5.0.*", // v5.0.11
        "twig/cssinliner-extra": "^2.12", // v2.14.3
        "twig/extensions": "^1.5", // v1.5.4
        "twig/extra-bundle": "^2.12|^3.0", // v3.3.0
        "twig/inky-extra": "^2.12", // v2.14.3
        "twig/twig": "^2.12|^3.0" // v2.14.4
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.0", // 3.4.0
        "fakerphp/faker": "^1.13", // v1.13.0
        "symfony/browser-kit": "5.0.*", // v5.0.11
        "symfony/debug-bundle": "5.0.*", // v5.0.11
        "symfony/maker-bundle": "^1.0", // v1.29.1
        "symfony/phpunit-bridge": "5.0.*", // v5.0.11
        "symfony/stopwatch": "^5.1", // v5.1.11
        "symfony/var-dumper": "5.0.*", // v5.0.11
        "symfony/web-profiler-bundle": "^5.0" // v5.0.11
    }
}

Previous Chapter

Next Chapter