/explore
|
You are here 
|
blog.bitexpert.de | ||
| | | | |
tomasvotruba.com
|
|
| | | | | With [Symfony 5 upgrade](/blog/2019/09/09/how-we-upgraded-pehapkari-cz-from-symfony-4-to-5-in-25-days/), we need any *working* Doctrine behaviors. Month later, we have [KnpLabs\DoctrineBehaviors 2.0](/blog/2019/12/30/doctrine-behaviors-2-0-reloaded/#how-do-you-migrate-from-gedmo-stof-to-knplabs-doctrinebehaviors) with full Symfony 5 support. If you used older Doctrine Behaviors, you're covered with Rector migration path. But what if you're using old broken Gedmo? **I'll show you how you can migrate Gedmo to KnpLabs**. | |
| | | | |
kokada.capivaras.dev
|
|
| | | | | ||
| | | | |
tomasvotruba.com
|
|
| | | | | This May will be released Symfony 3.3 with many DependencyInjection improvements. Each of them is quite nice, but combined together - they are huge jump compare to what we have now. Today I will show you what code can you drop and how to migrate it. | |
| | | | |
sookocheff.com
|
|
| | | Inversion of Control (IoC), also known as Dependency Injection (DI), allows an object to define their dependencies as constructor arguments (strictly speaking, you can set these dependencies as properties, but the examples I will use today are constructor-based). This is the inverse of the object itself controlling the instantiation or location of its dependencies, hence the name Inversion of Control. Let's look at an example from Stackoverflow using a text editor with a spell checking component: | ||
