You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
XCode 11 introduced @IBSegueAction as a new way for injection dependencies in VC modules. The new way suggests using new init(coder: ...) constructors. It broke up the current storyboard integration trick.
container.register(tag:"myVC"){MyViewController() << not compile now assoon a new designated initializer now called
}
Is there a way to use @Injected property wrappers or resolvingProperties callback in that case? Or maybe another workaround for using Storyboards alongside with IBSegueAction and Dip?
The text was updated successfully, but these errors were encountered:
init?(coder:NSCoder, dependency:String){self.dependency = dependency
super.init(coder: coder)}@available(*, unavailable)requiredinit(coder _:NSCoder){fatalError("NSCoding not supported")}convenienceinit(){fatalError("init should not be called directly")}
XCode 11 introduced @IBSegueAction as a new way for injection dependencies in VC modules. The new way suggests using new
init(coder: ...)
constructors. It broke up the current storyboard integration trick.Is there a way to use
@Injected
property wrappers orresolvingProperties
callback in that case? Or maybe another workaround for using Storyboards alongside with IBSegueAction and Dip?The text was updated successfully, but these errors were encountered: