Moya VS Swinject

In terms of dependencies, I always use Moya. It's a bit heavy, and it's not perfect, but holy hell is it better than nearly every networking layer written "from scratch" I've seen on nearly every project I've worked on. It's amazing to organize requests in a predictable way, have testing baked into the framework, and has first-class support for RxSwift/Combine. I can't recommend it enough.

Friends who are familiar with swift should know an excellent three party library Moya, the plugin version of the network request is really fragrant, so I use the idea to make a pure oc version of the plugin Network request library.

Moya - Network abstraction layer written in Swift. Language: Swift.

What is the advantage of your library over established solutions like Moya or protocol oriented networking approaches?

DI is a concept which makes a class independent of its dependency management. It achieves that by decoupling the usage of an object from its creation. This helps you to follow SOLID’s dependency inversion and single responsibility principles. To achieve this in Swift one of the most appreciated library is Swinject. This library not only provides DI but also have many other features like:-

Swinject - Dependency injection framework for Swift. Language: Swift.

We use Swinject which is probably quite similar https://github.com/Swinject/Swinject

So, how do we fix this? There is a cleaner solution. By using a dependency injection framework, such as Swinject we can create a base module that we might call the DI module.