I already talked about the subject of Dependency Inversion here and of course the way to implement Dependency Inversion is to use Dependency Injection.
First let’s go back to what is Dependency Injection. Dependency injection is used to inject real implementations into a class that uses abstract interfaces instead. So let’s say a Presenter Class uses of View Class. If you are using SOLID, then your Presenter Class will “see” the View Class thru an abstract interface (a contract) and thus the dependency to the View Class will be reversed as you can see in the Fig-1.
When this is done, you can “insert” whatever View in the Presenter as long as it respects the View Protocol contract.
To do the insertion, you will use Dependency Injection. There are 2 types of Dependency Injection :
To give a conclusion to this subject treated in Part1 and Part2, I want to go back to how native module work and how to communicate between native modules and ReactNative modules.
First, let’s talk about the .m file that enables to link native to JS thru runtime. The code was this :
In Part 1, we saw how to integrate ReactNative inside a Swift project using Cocoapods. Now, before starting to create a ReactNative View and integrate it into our project.
First, let’s take a quick tour of how ReactNative works.
I will not dive in depth (first because I don’t have enough expertise so far and second because it could take a complete book to make it) but at least I will reveal a little bit of the magic behind ReactNative from what I understood and read. There’s a very nice talk from Peggy Rayzis about this subject that you can watch here.
Continue reading “ReactNative Native Modules in Swift – Part 2 (ReactNative bridging)”
So I was working on a clean architecture example in Swift based on this post and the way I implement VIPR. I was adding/implementing a simplified version of it based on the graph represented in Fig-1.
And then I decided to prove that this architecture is really decoupled and thus wanted to integrate a ReactNative View into it. Of course I was overestimated my knowledge of ReactNative because I did few small projects in ReactNative and it looked very easy (because I was not bridging to native modules…). Continue reading “ReactNative Native Modules in Swift – Part 1 (Install ReactNative inside a Swift project…)”
Of course it’s impossible to answer this question in one single post, or even in one single book (the best known book for this is the one from M.Feathers, “Working Effectively with Legacy Code” that you can buy here). In fact it’s impossible to answer this question at all as it will all depend on what is the current status of what you have to refactor and every situation is specific. But still, there are few things that can be said and that can/should be applied when it’s about refactoring. Continue reading “Help, I need to refactor, but where should I start ? (SDP to the rescue)”
For this week, I want to give a clear example of the type of architecture that I’m trying to push on the projects I work on. Some of you probably already know VIPER. It tends to become a classical architecture in iOS development and in other platforms like Android. VIPER goes for :
In general, MVP (Model View Présenter/Controller) is a very nice pattern presented in many different languages and used in tons of development, especially when it’s about frontend.
On paper, MVP looks like in Ref – 1. That’s fine and as you can see, Presenter seems to depend on both the View and the Model. Continue reading “MVP pattern thru Dependency Inversion !”
You probably use models in your code every day and so do I. The major problem with a model is that it will surely evolve. It will evolve because the business will require a change or because a new feature will be needed and thus will require the model to change or because the api will have new fields or different informations. The best case is that this evolution will not touch your code, the worst case is that this evolution will destroy your code. But in any case you depend on this model and this is generally bad… Continue reading “Protect yourself from models !”
Dependency Inversion is a very simple concept : “if a class B depends on a class A, you can revert this dependency by generating a contract that class A must implement”. Thus you became responsible for this contract and you do not depend anymore on anyone because they will have to implement your contract and not you… Continue reading “What is Dependency Inversion ?”
One of the first thing that made me think that architecture mattered was when I discovered what Dependency Inversion was all about.
First I was generally mixing Dependency Inversion and Dependency Injection. For sure you better associate them but they can be used independently if you want. To me Dependency Injection was about : I want to have a class and be able to use it with what I want and I want to be the master of this. It was also the D letter in the acronym SOLID (this is wrong if you don’t know… 🙂 D is for Dependency Inversion). I was even pushing this during interviews and I was fully wrong… Continue reading “How I discovered Dependency Inversion…”