/explore
|
You are here 
|
matthiasnoback.nl | ||
| | | | |
tomasvotruba.com
While working with legacy projects, I often encountered this anti-pattern of misusing repositories. Instead of easy-to-inject service, projects are locked into a service locator. This makes code hard to upgrade and locks your project heavily to the Doctrine ODM packages. And there are plenty of them. Each extra package bites off its share of upgrade costs. Today, we look at how to refactor the ODM service locator to independent services and separate your project from ODM. We also get a few advantages in strict type coverage. |
|
| | | | | ||
| | | | |
jurian.slui.mn
|
|
| | | | | ||
| | | | |
qafoo.com
When you are refactoring in a legacy codebase, the goal is often to reduce complexity or separate concerns from classes, methods and functions that do too much work themselves. Primary candidates for refactoring are often controller classes or use-case oriented service classes (such as a UserService). Extracting new service classes is one popular refactoring to separate concerns, but without tests it is dangerous because there are many ways to break your original code - we show you how this can still be done. |
|
| | | | | ||
| | | | |
nodogmablog.bryanhogan.net
Setting up dependency injection for your .NET Lambda functions only takes a few lines of code. Read on to see how. |
|
| | | |||
