SwiftyViperTemplates

Collection of Generamba VIPER templates.

Usage

create Rambafile at the root of your project folder.
add templates description to it (see below)
setup all variables
in 'Templates' section define all templates or only some them.
open terminal in project folder
install Generamba
run:

generamba template install

generamba will fetch required templates to "./Templates" folder
now you can generate any new module using generamba:
generamba gen MyModuleName SwiftyViperMcFlurryAlert
also you can pass additional keys to generamba (see keys supported by these templates):
generamba gen MyModuleName SwiftyViperMcFlurryAlert --custom_parameters extended_configure:true
most of the templates requires additional pods installed, see concrete template description

Short names of templates

tabbar = SwiftyViperMcFlurryTabbar
service = SwiftyViperService
default = SwiftyViperMcFlurryStoryboard
alert = SwiftyViperMcFlurryAlert
container = SwiftyViperMcFlurryEmbedStoryboard
collection_as_root_and_cachetracker = SwiftyViperMcFlurryStoryboardRootCollectionViewCacheTracker
collection_as_root_with_embeddables_and_cachetracker = SwiftyViperMcFlurryStoryboardComplexRootCollectionViewCacheTracker
collection_as_secondary_and_cachetracker = SwiftyViperMcFlurryStoryboardCollectionViewCacheTracker
collection_as_secondary_with_embeddables_and_cachetracker = SwiftyViperMcFlurryStoryboardComplexCollectionViewCacheTracker
table_as_root_and_cachetracker = SwiftyViperMcFlurryStoryboardRootTableViewCacheTracker
table_as_root_with_embeddables_and_cachetracker = SwiftyViperMcFlurryStoryboardComplexRootTableViewCacheTracker
table_as_secondary_and_cachetracker = SwiftyViperMcFlurryStoryboardTableViewCacheTracker
table_as_secondary_with_embeddables_and_cachetracker = SwiftyViperMcFlurryStoryboardComplexTableViewCacheTracker
transparent = SwiftyViperMcFlurryTrasparent

Special templates

Most of the templates generate UI modules, but some of them generate lowe level logic modules: services.
In project structure services code is located usually in different place than UI. So whil generation you should
pass another path for new module location. This can be achieved by passed special keys to generamba:

--module_path
--test_path

generamba gen My service --module_path MyApp/Services

or if you use tests

generamba gen My service --module_path MyApp/Services --test_path MyAppTests/Services

More generamba info you can find at generamba commands

Custom keys

Keys passed with --custom_parameters to generamba.

generamba gen MyModuleName SwiftyViperMcFlurryAlert --custom_parameters key1:value1 key2:value2 ...

extended_configure:true

Usefull when configuration of module is not trivial.
If passed as true:

generamba gen MyModuleName SwiftyViperMcFlurryAlert --custom_parameters extended_configure:true

then configure() method of module input will be generated as:

struct MyModuleConfig {
    // TODO: Place your code here
}

protocol MyModuleInput: AnyObject {

    func configure(with config: MyModuleConfig)

}

In this case you can add more parameters while development to MyModuleConfig without modifying existing code.

embeddable_extended_configure_vars

NOTE: Parameter make sense for templates where embeddable module used only (SwiftyViperMcFlurryStoryboardComplexRootTableViewCacheTracker, etc...).

If defined, then configuration method of embeddable module will generated with input object.