Swift protocols for VIPER from Siberia with love!
Swift >4.0, iOS version >= 9.0
SiberianVIPER is available through CocoaPods. To install it, simply add the following line to your Podfile:
2.0.2 and 3.0.* versions are not fully compatible. You'll need to specify pod version.
To install SiberianVIPER you can also use Carthage. Just add the following to your Cartfile:
You can find an example usecase of SiberianVIPER. See kindly attached Example project. Modules have been generated by VIPERTemplates (see the link above). VIPERTemplates also go with a couple of snippets for fast cell-cellModel pairs creation.
Sergey Petrachkov, [email protected]
Some easy steps
- Create a fork.
- Checkout develop.
- Use gitflow to create a feature branch.
- Implement your thing.
- Clean code if needed.
- Submit pull request.
How to write commits messages?
Not only a commit message must contain a short description of changes done in this commit but a short description of why any work had been done. Every developer can see the difference between two commits but it's very important to know why it has been done.
Bad commit message example:
Good commit message example:
updated DummyViewController with dummy things to match another dummy thing
or even better:
refs #999 - fixed bug where app would crash when entering DummyViewController the reason of crash was incorrect handling of setup values"
Another idea is to add references to tickets one's working on. Popular management systems like unfuddle or redmine can monitor repositories and link commits to tickets, so a customer or a project manager/ teamleader or a person who performs code review can just open a ticket and see all the work done for that ticket.