vipergeng 0.2.12 → 0.2.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 5a47e63d5548580787230989e2c4d90492ba3761
|
4
|
+
data.tar.gz: 0f602a320092c9ce92dfc2a945018e1064040ec8
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 1372d40fed254b4d23bda53f1fc1c585430927181dbc34765023d556ff201943bd5fd1a326364ed73fafaac121b0048056f40cb82a31dc6bec2dbfb278dedfb6
|
7
|
+
data.tar.gz: 4b398485eedfc8a5e6d5f655df47641ed7ed605d43711455ea0da1c654df43e9bc2a173b68d57087d9a210cc9ade71e3d34e454f686fabceced9765568dd7646
|
data/README.md
CHANGED
@@ -1,4 +1,4 @@
|
|
1
|
-
Viper Module Generator
|
1
|
+
Viper Module Generator G version
|
2
2
|
======================
|
3
3
|
[](https://codeclimate.com/github/teambox/viper-module-generator)
|
4
4
|
[](https://travis-ci.org/teambox/viper-module-generator)
|
@@ -42,8 +42,8 @@ The implementation scheme returned by this generator is hardly inspired in the e
|
|
42
42
|
- Add `COMPANY` parameter to set the company name on the files header
|
43
43
|
- Set Swift as the default language
|
44
44
|
|
45
|
-
###
|
46
|
-
-
|
45
|
+
### Changelog 0.2.12
|
46
|
+
- Add `PROJECT` parameter to set the company name on the files header
|
47
47
|
|
48
48
|
## Viper files structure
|
49
49
|
```bash
|
@@ -82,38 +82,29 @@ The implementation scheme returned by this generator is hardly inspired in the e
|
|
82
82
|
## How to install vipergen ?
|
83
83
|
You can install it easily as using the gem. With ruby installed in your OSX execute:
|
84
84
|
```bash
|
85
|
-
sudo gem install
|
85
|
+
sudo gem install vipergeng
|
86
86
|
```
|
87
87
|
If everything were right, you should have now the vipergem command available in your system console
|
88
88
|
|
89
89
|
## How to generate a VIPER module with a given name?
|
90
90
|
You have just to execute the following command
|
91
91
|
```bash
|
92
|
-
|
92
|
+
vipergeng generate MyFirstViperModule --path=~/myproject/shared
|
93
93
|
```
|
94
94
|
Another example:
|
95
95
|
```bash
|
96
|
-
|
96
|
+
vipergeng generate MySecondViperModule --path=~/myproject/shared --author='My Name' --company='My Company' --template='existing_template' --project='project name' --language=swift
|
97
97
|
```
|
98
98
|
|
99
99
|
And then the files structure will be automatically created. Don't forget to add this folder to your project dragging it into the XCode/Appcode inspector
|
100
100
|
|
101
|
-
## How can I try the demo project?
|
102
|
-
|
103
|
-
1. Clone the repo `git clone https://github.com/pepibumur/viper-module-generator.git`
|
104
|
-
2. Move into the repo folder and update the git submodules `git submodule update --init`
|
105
|
-
3. In the folder VIPERGenDemo install the pods `pod install`
|
106
|
-
4. Open the project from the `VIPERGenDemo.xcworkspace` file
|
107
|
-
5. Enjoy it!
|
108
|
-
|
109
|
-
|
110
101
|
## Developer tips
|
111
102
|
### Update the gem
|
112
103
|
When the gem is updated it has to be reported to the gem repository. I followed this tutorial http://amaras-tech.co.uk/article/43/Creating_executable_gems that basically says that once you have your gem ready execute:
|
113
104
|
```bash
|
114
|
-
gem build
|
115
|
-
gem install
|
116
|
-
gem push
|
105
|
+
gem build vipergeng.gemspec
|
106
|
+
gem install vipergeng-0.1.gem
|
107
|
+
gem push vipergeng-0.1.gem
|
117
108
|
```
|
118
109
|
Then you'll be asked for your credentials in order to make the update in the repo (http://guides.rubygems.org/publishing/)
|
119
110
|
|
data/lib/vipergen/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: vipergeng
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.2.
|
4
|
+
version: 0.2.13
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Pedro Piñera
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2017-06-
|
11
|
+
date: 2017-06-02 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: rake
|
@@ -113,7 +113,7 @@ files:
|
|
113
113
|
- lib/templates/default/swift/Interactor/VIPERItem.swift
|
114
114
|
- lib/templates/default/swift/Presenter/VIPERPresenter.swift
|
115
115
|
- lib/templates/default/swift/Protocols/VIPERProtocols.swift
|
116
|
-
- lib/templates/default/swift/View/
|
116
|
+
- lib/templates/default/swift/View/VIPERViewController.swift
|
117
117
|
- lib/templates/default/swift/WireFrame/VIPERWireFrame.swift
|
118
118
|
- lib/templates/default/viperspec.yml
|
119
119
|
- lib/templates/naja/swift/Interactor/VIPERInteractor.swift
|
@@ -152,7 +152,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
152
152
|
version: '0'
|
153
153
|
requirements: []
|
154
154
|
rubyforge_project:
|
155
|
-
rubygems_version: 2.
|
155
|
+
rubygems_version: 2.6.8
|
156
156
|
signing_key:
|
157
157
|
specification_version: 4
|
158
158
|
summary: Generates XCode VIPER module controllers structure
|
File without changes
|