In just 3 lines of code
@Push(makeHome)varhomefunc makeHome(model:HomeModel)->HomeView{HomeView(model: model)}route(to: \.home,HomeModel(username: username, password: password))Implement a SwiftUI App
@mainstructNavigationApp:App{privateletcoordinator=AppCoordinator(())varbody:someScene{WindowGroup{ coordinator.makeView()}}}
This is a standard implementation for a 100% SwiftUI app.
Implement your first coordinator
import GoodCoordinator finalclassAppCoordinator:NavigationCoordinator{typealiasInput=VoidtypealiasOutput=Voidvarstate:NavigationStack=.init()@Root(makeRoot)varrootfunc makeRoot()->InitialView{InitialView() /// SwiftUI View! }}
Don't worry about code you don't understand yet. Feel free to name the
makeRootfunction in any way you prefer. The function returns the view of your choice. However, to get this code to compile, you need to do one more thing:Modify your SwiftUI View a bit
import GoodCoordinator struct InitialView:View,Screen{ /// Extend from Screen as well ...
Add a navigation step
@Push(makeNewScreen)varopenNewScreenfunc makeNewScreen()->NewScreen{NewScreen(viewModel:NewScreenViewModel())}
Add a step into your coordinator and specify, how the view will get constructed.
Navigate!
@EnvironmentObjectvarrouter:Router<AppCoordinator> // SwiftUI view code Button("Go to new screen"){ router.coordinator.route(to: \.openNewScreen)} // More SwiftUI view code
Launch the navigation step from your view.
structLogger:CoordinatorLogger{func logCoordinatorEvent(_ message:Any, level:LogLevel, fileName:String, lineNumber:Int){print("[\(level.rawValue)] \(message) [\(fileName):\(lineNumber)]")}}CoordinatorConfiguration.logger =Logger()You can use Swift Package Manager (SPM) to import this package. Use the following URL:
https://github.com/GoodRequest/GoodCoordinator-iOS.git
Set your datatype as an Input
Modify the navigation step that requires input data - add the data as a parameter.
Note: navigation steps are limited to 1 input parameter only. This is due to practical reasons, as adding 2 or more input parameters would require disproportional amount of additional function overloads in the code base. If you require multiple input parameters, consider making a
structout of them and pass the struct.finalclassMyCoordinator:NavigationCoordinator{...func makeRoot(someData:String)->RootView{RootView(model:RootModel(data: someData))}...}
If your input view is the
@Rootstep of a coordinator, change the whole coordinator Input typealias to reflect your datatype:typealiasInput=String
Navigate
In a SwiftUI view:
@Stateprivatevarusername:String=""...Button("Push with data"){ router.coordinator.route(to: \.step, username)}
Call the route function with additional parameter as an input. Xcode should automatically autocomplete this function with expected data type.