Chapters

14 Chapters | 1:49:07 |

01

Patrones de diseño y sus tipos

6:00
02

Patrón de estrategia

10:09
03

Estrategia Parte 2: Beneficios y en la naturaleza

9:43
04

Patrón constructor

7:30
05

Mejoras en el constructor

7:02
06

Constructor en Symfony y con una Fábrica

8:18
07

El patrón del observador

7:24
08

La clase observadora

5:37
09

Observador dentro de Symfony + Beneficios

11:08
10

Publicar-Suscribir (PubSub)

6:18
11

Clase de evento Pub Sub y suscriptores en Symfony

6:34
12

El patrón decorador

8:53
13

Decoración con el contenedor de Symfony

4:35
14

Decoración: Anular los servicios del núcleo y AsDecorator

9:56

> OOP > Patrones de Diseño para Divertirse y Subir de Nivel

Buy Access to Course

06.

Constructor en Symfony y con una Fábrica

|

|

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

Previous Chapter

Next Challenge

Script
Comments

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

4 Comments

Sort By

Login or Register to join the conversation

Kacper-G 3 years ago

Sorry I had a little trouble with understanding why CharacterBuilderFactory is a service and CharacterBuilder is not.
So in my understanding a typical class is not a service and cannot autowire until it is autowired by another class (in this example GameApplication)?

|

MolloKhan SFCASTS Kacper-G 3 years ago

Hey Kacper,

The intention of the CharacterBuilderFactory is to allow us to instantiate as many CharacterBuilder objects as we want. In this case, we can't reuse the same instance of a CharacterBuilder because after you use it to create a Character object it holds state (health, damage, armor, etc.), so, instead of clearing the state we just instantiate another builder object. It was done this way for convenience and for quickly talking about the factory pattern.

Cheers!

2 |

Sargath 3 years ago edited

Well, even though CharacterBuilder is not a service, after we add LoggerInterface to its constructor, it will be autowired by a container, as well ass injected by the factory. Shouldn't namespace of the builder be excluded from auto-wiring in the configuration, to actually inject it only by the factory?

|

Victor SFCASTS Sargath 3 years ago edited

Hey Sargath,

Good question. At this exact moment, it makes sense to exclude that CharacterBuilder from the auto-wiring configuration. Though, further in the course, we will rewrite it into a Symfony service. So, for simplicity, we do not focus on this too much right now, i.e. because eventually, we want it to be a real service in our Symfony app.

But if you want to leave the code as it is in this specific chapter - yeah, you can ignore it which makes more sense :) Though, while you're not using that CharacterBuilder as a service anyway - it's still no that much important ;)

Anyway, a good catch ;)

Cheers!

|

Previous Chapter

Next Challenge