Dependency Injection part 2
Dependency Injection We have seen that we can utilize the Apex Type class to give us some kind of "dynamic processing", well, not quite yet. It's true that we can simplify things now but there are a couple of components in our structure that are still missing. So far we have one interface and two classes that are implementing our interface. Now we are going to add the dynamic part that makes dependency injection so powerful. All we want is to supply our code with the correct class based on the user that is executing the apex transaction. We want this to be dynamic and we want one line of code to make that decision for us. Should I go 'right', should I go 'left'... we need to control de 'cross-road' and…