/explore
|
You are here 
|
blog.bitexpert.de | ||
| | | | |
kokada.capivaras.dev
|
|
| | | | | ||
| | | | |
tomasvotruba.com
Dependency injection with autowiring is super easy [since Symfony 3.3](/blog/2017/05/07/how-to-refactor-to-new-dependency-injection-features-in-symfony-3-3/). Yet on my mentoring I still meet service locators. Mostly due to traditional registration of Doctrine repositories. The way out from *service locators* to *repository as service* was [described](https://matthiasnoback.nl/2014/05/inject-a-repository-instead-of-an-entity-manager) by many [before](https://medium.com/@adamquaile/composition-over-inheritance-in-doctrine-repositories-f6a53a026f60) and **now we put it into Symfony 3.3 context**. |
|
| | | | | ||
| | | | |
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**. |
|
| | | | | ||
| | | | |
brunoscheufler.com
JSON Web Tokens are a popular way of managing authorization and authentication policies for web applications. Sending around a base64-encoded token that can be verified by every service using it, enables uncomplicated (and stateless) application design compared to other mechanisms.... |
|
| | | |||
