When you decide to use VIPER architecture in your project, it is very tired create new modules, because you need create at least 5 files for each. Imagine that you need to create 6 modules...I was suffering this problem, and this is the raison why I've created this template. It's very useful for me and I hope that for you too.
Only need execute this command in terminal:
sudo swift install.swiftYou should be this output message:
If all it's ok you now could find your template in Xcode.
Go to Application folder, browse to the Xcode application icon. Right-click it and choose 'Show Package Contents'. Then browse to:
Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Xcode/Templates/Project Templates/iOS/Application and add "Module VIPER.xctemplate" file. Now you can find your template in Xcode.
This template generates all files that you need to create a new VIPER module. All generated code is Swift 3.
This is an example, we're creating a Login module:
After using VIPER, I've found it to be very beneficial in many ways. Let’s get back to the list of things we set out to accomplish when architecting our app to see if VIPER addresses them.
- Easy to iterate on
- Collaboration friendly
- Separated out concerns
- Spec-ability
Would you like decide what will be the next feature? now, you can do it here
- Create bash script to install more easy
- Divide Interactor protocol (Input & Output) (NEW! Version 1.1)
- Swift 4 & XCode 9 (NEW! Version 1.2)
- Add Dependency Injection Framework
- Customize name of components
-
Create groups in template(Only available for Project templates)
- iOS Architecture Patterns
- #8 VIPER to be or not to be?
- https://www.objc.io/issues/13-architecture/viper/
- https://www.ckl.io/blog/ios-project-architecture-using-viper/
This is an open source project, so feel free to contribute. How?
- Open an issue.
- Send feedback via email.
- Propose your own fixes, suggestions and open a pull request with the changes.
- Juanpe Catalán 🐦