Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

More robust assets path 👍 #24

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

More robust assets path 👍 #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,18 +20,18 @@ Go to Application folder, browse to the Xcode application icon. Right-click it a
`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.

## Easy to use
![](/assets/wizard.png)
![](assets/wizard.png)

## Generated code
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:

- [Default, without divide](/assets/defaultOutput.md)
- [With divided Interactor (Input & Output)](/assets/inputOutput.md)
- [Default, without divide](assets/defaultOutput.md)
- [With divided Interactor (Input & Output)](assets/inputOutput.md)

## VIPER diagram overview
![Preview](/assets/viper_diagram.png)
![Preview](assets/viper_diagram.png)

## Why VIPER?
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.
Expand Down