Viper Framework for iOS using Swift

Do you think it is possible to add availability for SwiftUI features in framework? I accidentally run into crash because of that :( Sth like #if isAvailable() or version check might be helpful :)

My failure was

dyld: Library not loaded: /System/Library/Frameworks/SwiftUI.framework/SwiftUI Referenced from: /Users/piotrgawlowski/Library/Developer/CoreSimulator/Devices/818027B6-FE01-489E-937A-E7764561A2CE/data/Containers/Bundle/Application/D9182AB1-13FE-40CE-A395-45E6B06EA2F4/eForskrivning.app/Frameworks/Viperit.framework/Viperit Reason: image not found

I've set optimization level "optimize for speed".

        let module = module.build()        
        module.router.show(from: viewController, embedInNavController: true, setupData: id)

embedInNavController: true seems to be crucial here.

I am calling router.show() with already existing navigation controller to archive card like presentation style with different navigation context.

In that situation app crashes because of nil _preseter. With optimization for speed turned off everything seems to be fine.

Any ideas how to handle? Currently I've turned off optimization.

I made a sample project named "Viper-Sample" and the Viper components created belong to "Viper_Sample" bundle namespace. So this fixes the classForViperComponent method returning nil.

WHAT WAS ADDED ? A modal presentation style has been added to show the view controller. Unit test was also added. FOR WHAT WAS ADDED ? This feature was necessary for the modal presentation display of controllers on the guidelines of Apple. Without this, you need to do the Router extension.

class HostingUserInterface - file UserInterface+SwiftUI.swift line 16 Incorrect argument labels in call (have 'nibName:bundle:', expected 'coder:rootView:')

There's an issue that happens only when downloading the app from testflight, otherwise running from Xcode works fine and I don't use storyboard or xib files it's only code

And here's the implementation

window = UIWindow(windowScene: scene)
let module = AppModules.splash.build()
module.router.show(inWindow: window, embedInNavController: false, setupData: nil, makeKeyAndVisible: true)

Hi,

interesting framework and library, I've two questions:

• If I need a custom UIViewController what do I have to do? I've to create a custom UserInterface that inherits from my custom UIViewController? I've seen that UserInterface inherits from UIViewController. Here (https://github.com/ferranabello/Viperit/issues/69) you say that we have to thins Eureka as a subview but it complicates things. If we want to simplify could we create a custom UserInterface. Could you give us an example?

• In you framework there's DisplayData. How should it be used?

Thanks

Hi! First of all - thank you for great framework! What is the best practice of integration of one module into another? E.g: ParentModule contains table, and the ChildModule contains view for ParentModule tableHeaderView. What is the proper way to integrate ChildModule into ParentModule? Thank you!

Could I get the sample format with Alamofire in Viperit like iOS-Viper-Architecture. And How do I create the storyboard for iPad and iPhone within one module because iPad and iPhone was difference Design? Thanks a lot.

I have build a project according to viperit instructions then app crashes on the start .That can be seen in screen shot .Here is my AppDelegate source ` import UIKit import Viperit enum AppModules: String, ViperitModule { case myFirstModule } @UIApplicationMain class AppDelegate: UIResponder, UIApplicationDelegate {

var window: UIWindow?


func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
    
    window = UIWindow(frame: UIScreen.main.bounds)
    let module = AppModules.myFirstModule.build()
    module.router.show(inWindow: window)
    return true
}

`

First of all let me congratulate you, this is the best approach to VIPER I have seen and it's close to mine but using a bigger knowledge on Swift.

But it doesn't compile against https://github.com/realm/SwiftLint , i can exclude your Pod from the listing process but as i rather to understand your source would be cooler if it were linted.

Even excluding Pods from the linting, the modules generated by the template includes at least two lint errors that could be easily fixed:

• the forced casts on VIPER componentes getters var presenter: LoginPresenter { return _presenter as! LoginPresenter }
• the use of underscore on the same VIPER componentes, on my VIPER architecture I called them proxyPresenter, proxyRouter...

Fatal error: Unexpectedly found nil while unwrapping an Optional value: file /Users/chris/Nutstore Files/XCode/VIPER/ViperItExample/Pods/Viperit/Viperit/Core/Module.swift, line 28 2020-06-13 12:05:39.324354+0800 ViperItExample[2698:112714] Fatal error: Unexpectedly found nil while unwrapping an Optional value: file /Users/chris/Nutstore Files/XCode/VIPER/ViperItExample/Pods/Viperit/Viperit/Core/Module.swift, line 28

func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) { // Use this method to optionally configure and attach the UIWindowwindowto the provided UIWindowScenescene. // If using a storyboard, thewindowproperty will automatically be initialized and attached to the scene. // This delegate does not imply the connecting scene or session are new (seeapplication:configurationForConnectingSceneSession` instead).

// guard let _ = (scene as? UIWindowScene) else { return }

    guard let scene = (scene as? UIWindowScene) else { return }

    window = UIWindow(frame: UIScreen.main.bounds)
    window?.windowScene = scene

    let module = AppModules.ceshi.build()
    let router = module.router as! CeShiRouter
    module.router.show(inWindow: window, embedInNavController: true, setupData: nil, makeKeyAndVisible: true)
    
}`

Is it any neat way to use one view (storyboard/xib/whatever) with multiple modules? Example: We've got same, template style overlay view. Let's call it ActionOverlayView. It has always exactly same construction: header, description, button1, button2 etc. but totally different behaviour. Once it will redirect to different parts of app, other time it's going to resend verification email, logout user etc. There is totally no point of copy pasting whole view only for the same of module.

That is why I think it might be useful to move viewIdentifier to ViperItModuleProtocol and allow us to change default viewIdentifier.

VipertitModuleProtocol var viewIdentifier: String? { get }

Module let viewIdentifier = module.viewIdentifier ?? safeString(NSStringFromClass(viewClass).components(separatedBy: ".").last)

In that case we might be able to use one view with multi-purpose modules.