SwiftLint VS Swinject

SwiftLint is a big one.

I actually don't see anything worth changing. It looks good to me. I think the most important thing is just to maintain the constructive attitude you already have about future-you dealing with the code, because only future-you will really know where you could have done better. One personal-preference thing I carried over from working on Go code is to look for a tool like gofmt [1,2] for Swift. I've been using swift-format [3] for about 2 years and haven't been dissatisfied enough to reach for something more fully featured like SwiftLint [4]. I didn't like the idea at first of delegating most formatting control over to a tool designed with someone else's subjective idea of formatting. But my feeling afterward was that it was freeing: it was no longer (completely) my job/burden/responsibility. An "assistant" would clean up the formatting of my code every time I saved the file. That's a nightmare if you can't configure the tool as much as you need, but if you're lucky and find a configuration you can live with, it lets you focus more on naming and other conventions that aren't so easily automated (yet). [1] https://go.dev/blog/gofmt [2] https://twitter.com/bitfield/status/953395343353315329 [3] https://github.com/apple/swift-format [4] https://github.com/realm/SwiftLint

iOS SwiftLint

1) Here are some tips & tricks for refactoring: https://developer.apple.com/documentation/xcode/finding-and-...

The “rename in project” or “rename in scope” functions are quite neat.

2) Check out SwiftLint: https://github.com/realm/SwiftLint

I have not used it in a while, but it comes with good defaults and is highly customizable to your own preferred Swift style.

Check this as well https://github.com/realm/SwiftLint

Try SwiftLint. https://realm.github.io/SwiftLint/

if which swiftlint >/dev/null; then swiftlint else echo "warning: SwiftLint not installed, download from https://github.com/realm/SwiftLint" fi

SwiftLint - A tool to enforce Swift style and conventions. Language: Swift.

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.