Latest 1.4.0
License MIT
Platforms ios 10.0, osx 10.11, tvos 12.2, watchos 5.2
Frameworks Foundation

Build Status
Code coverage status
Platform support
Carthage Compatible
CocoaPods Compatible
License MIT


Let’s say you have a table view controller that displays privileged information once a user selects a cell. An implementation of tableView:didSelectRowAtIndexPath: may look as such.

override func tableView(tableView: UITableView, didSelectRowAtIndexPath indexPath: NSIndexPath) {
    switch Row(rawValue: indexPath.row)! {
    // ...
    case .PrivilegedInfo:
    // ...

Perhaps the privileged information is only available after a user authenticates with the service. After logging in we want the privileged information presented to the user right away. Without changing the above implementation we may proxy the intent and display a log in view, after which, a call back may present the privileged information screen.

router.proxy("/*/privilegedinfo", tags: ["Views"]) { route, parameters, any, next in
    if authenticated {
    } else {
        next(("routingexample://present/login?callback=(route)", parameters, any))

Routing Proxy

Eventually we may need to support a deep link to the privileged information from outside of the application. This can be handled in the AppDelegate simply as follows.

func application(app: UIApplication, openURL url: NSURL, options: [String : AnyObject]) -> Bool {
    return router["Views"].open(url)

Routing Deep Link

An example of other routes in an application may look like this.

let presentationSetup: PresentationSetup = { vc, _, _ in
    vc.navigationItem.leftBarButtonItem = UIBarButtonItem(barButtonSystemItem: .cancel,
                                                          target: vc,
                                                          action: #selector(vc.cancel))
           source: .storyboard(storyboard: "Main", identifier: "LoginViewController", bundle: nil),
           style: .inNavigationController(.present(animated: true)),
           setup: presentationSetup)"routingexample://push/privilegedinfo",
           source: .storyboard(storyboard: "Main", identifier: "PrivilegedInfoViewController", bundle: nil),
           style: .push(animated: true))"routingexample://present/settings",
           source: .storyboard(storyboard: "Main", identifier: "SettingsViewController", bundle: nil),
           style: .inNavigationController(.present(animated: true)),
           setup: presentationSetup)

router.proxy("/*", tags: ["Views"]) { route, parameters, any, next in
    print("opened: route ((route)) with parameters ((parameters)) & passing ((any))")

At its simplest, Routing allows the association of string patterns to closures. This allows for the expression of intent in certain areas of code and the implementation of it in another. UI may only be concerned with expressing the intent of transitioning to another view and the business logic may be handled elsewhere. Routing allows for the explicit documentation of an application’s behavior and views through mappings and proxies.



Via CocoaPods:

source ''
platform :ios, '10.0'

pod 'Routing', '~> 1.4.0'


Via Carthage:

github "jjgp/Routing"

Further Detail


A router instance may map a string pattern to view controller navigation, as covered in the Usage section above, or just a closure as presented below. The closure will have four parameters. The route it matched, the parameters (both query and segments in the URL), any data passed through open, and a completion closure that must be called or the router will halt all subsequent calls to #open."routingexample://route/:argument") { route, parameters, any, completed in
    argument = parameters["argument"]


A router instance may proxy any string pattern. The closure will also have four parameters. The route it matched, the parameters, any data passed, and a next closure. The next closure accepts a ProxyCommit? tuple with arguments String, Parameters, and Any?. If nil is passed to Next then the router will continue to another proxy if it exists or subsequently to a mapped route. If a proxy were to pass a ProxyCommit tuple to the next closure, the router will skip any subsequent proxy and attempt to match a mapped route. Failure to call next will halt the router and all subsequent calls to #open.

router.proxy("routingexample://route/one") { route, parameters, any, next -> Void in
    next(("routingexample://route/two", parameters, any))

Order of Map or Proxy

In general, the last call to register a map or proxy to the router will be first called in the event of a matched URL respectively. Proxies will be serviced first and then a map.


A tag may be passed to maps or proxies. The default tag for maps to view controller navigation is "Views". Tags allow for the router to be subscripted to a specific context. If a router is subscripted with "Views", then it will only attempt to find routes that are tagged as such.

router.proxy("/*", tags: ["Views, Logs"]) { route, parameters, any, next in
    print("opened: route ((route)) with parameters ((parameters)) & passing ((any))")

router["Views", "Logs", "Actions"].open(url)

router["Views"].open(url, passing: NSDate()) // pass any data if needed // - or - to search all routes...

Route Owner

Routes may have a RouteOwner specified when using #map or #proxy. When the RouteOwner is deallocated, the route is removed from the Routing instance.

public protocol RouteOwner: class {}

class PrivilegedInfoViewController: UIViewController, RouteOwner {
    override func viewDidLoad() {"routingexample://secret",
                   owner: self,
                   source: .storyboard(storyboard: "Main", identifier: "SecretViewController", bundle: nil),
                   style: .push(animated: true))

RouteUUID and Disposing of a Route

When a route is added via #map or #proxy, a RouteUUID is returned. This RouteUUID can be used to dispose of the route.

routeUUID ="routingexample://present/secret",
                       source: .storyboard(storyboard: "Main", identifier: "SecretViewController", bundle: nil),
                       style: .inNavigationController(.present(animated: true)))

router.dispose(of: routeUUID)

Callback Queues

A queue may be passed to maps or proxies. This queue will be the queue that a RouteHandler or ProxyHandler closure is called back on. By default, maps that are used for view controller navigation are called back on the main queue.

let callbackQueue = DispatchQueue(label: "Call Back Queue", attributes: [])"routingexample://route", queue: callbackQueue) { _, _, _, completed in

Presentation Setup

View controllers mapped to the router will have the opportunity to be informed of a opened route through either a closure or the RoutingPresentationSetup protocol. In either implementation, the view controller will have access to the parameters passed through the URL. An example of the closure approach is in the Usage section above. The protocol looks as follows.

class LoginViewController: UIViewController, RoutingPresentationSetup {
    var callback: String?

    func setup(_ route: String, with parameters: Parameters, passing any: Any?) {
        if let callbackURL = parameters["callback"] {
            self.callback = callbackURL

        if let date = any as? NSDate {
            self.passedDate = date

Presentation Styles

indirect public enum PresentationStyle {
    case show
    case showDetail
    case present(animated: Bool)
    case push(animated: Bool)
    case custom(custom: (presenting: UIViewController, presented: UIViewController, completed: Routing.Completed) -> Void)
    case inNavigationController(Routing.PresentationStyle)

The above presentation styles are made available. The recursive .InNavigationController(PresentationStyle) enumeration will result in the view controller being wrapped in a navigation controller before being presented in whatever fashion. There is also the ability to provide custom presentation styles.

View Controller Sources

The following view controller sources are utilized.

public enum ControllerSource {
    case storyboard(storyboard: String, identifier: String, bundle: NSBundle?)
    case nib(controller: UIViewController.Type, name: String?, bundle: NSBundle?)
    case provided(() -> UIViewController)

Presentation Extensions

The following has been extended to allow for a completion closure to be passed in.

extension UIViewController {
    public func showViewController(vc: UIViewController, sender: AnyObject?, completion: Routing.Completed)
    public func showDetailViewController(vc: UIViewController, sender: AnyObject?, completion: Routing.Completed)

extension UINavigationController {
    public func pushViewController(vc: UIViewController, animated: Bool, completion: Routing.Completed)
    public func popViewControllerAnimated(animated: Bool, completion: Routing.Completed) -> UIViewController?
    public func popToViewControllerAnimated(viewController: UIViewController, animated: Bool, completion: Routing.Completed) -> [UIViewController]?
    public func popToRootViewControllerAnimated(animated: Bool, completion: Routing.Completed) -> [UIViewController]?

Latest podspec

    "name": "Routing",
    "version": "1.4.0",
    "summary": "A Swift router implementation",
    "description": "Routing allows for routing URLs matched by string patterns to associated closures.",
    "homepage": "",
    "license": {
        "type": "MIT",
        "file": "LICENSE"
    "authors": {
        "Jason Prasad": "[email protected]"
    "source": {
        "git": "",
        "tag": "1.4.0"
    "platforms": {
        "ios": "10.0",
        "osx": "10.11",
        "tvos": "12.2",
        "watchos": "5.2"
    "frameworks": "Foundation",
    "ios": {
        "frameworks": [
        "source_files": "Source/iOS.swift"
    "source_files": "Source/Ro*.swift"

Pin It on Pinterest

Share This