Are we really limited to 10 potential routes per view? about swiftui-router HOT 3 CLOSED

A single Switch with a large number of Routes as its descendants would indeed have an (albeit tiny) impact on performance. For this it's advised to slice your routing in multiple Switches to utilize early elimination.

Taking your initial example: an app that has a route for each tab, you could implement the navigation similar to:

// Create routes for every tab in the app.
struct RootView: View {
    var body: some View {
        Switch {
            Route(path: "/news", content: NewsView)
            Route(path: "/finances", content: FinancesView)
            Route(path: "/twitter", content: TwitterView)
            // etc...
        }
    }
}

// Create routes for the news tab.
struct NewsView: View {
    var body: some View {
        Switch {
            Route(path: "/news/latest", exact: true, content: LatestNewsView)

            // Parameter variables coming in a future version. :)
            Route(path: "/news/:newsId", exact: true) { routeProps in 
                NewsItemView(id: routeProps.params.newsId)
            }

            // Default view.
            Route(content: NewsHomeView)
        }
    }
}

(Pardon the crude example 😅)

Let's say the app's current path was /finances. In the first Switch, the /news Route will be tested, fail, and prevent the need to test all sub-routes in NewsView.

By splitting the branches into multiple views (and thus multiple Switches) you utilize early elimination, preventing a Switch from checking for (too many) unnecessary routes. This should help performance wise while also making the code easier to read.

Anyway, thanks for checking out SwiftUI Router! 😄

from swiftui-router.

Explained it perfectly, thanks!

The Groups seem like a decent workaround, especially if the implementation details are abstracted into something prettier. Still a bit fragile looking and I wonder if there could be performance impacts for a switch with an especially large about of routes.

Appreciate the POC and the clarification 👍

from swiftui-router.

The limit of 10 direct descendant views comes from the limitation of @ViewBuilder and TupleView. You can theoretically have infinite routes in your app. But like every other View using @ViewBuilder (like Group, HStack, VStack, etc.) you can't put more than 10 Routes as direct descendants in a Switch. This isn't a limit of SwitchUI Router, but rather a limit in SwiftUI (and I think Swift 5.1 at this point?)

To illustrate:

Switch {
    // You can only put a maximum of 10 children here.
}

To bypass this limitation, you should be able to divide your collection of Routes in Groups!

Switch {
    Group {
        // Put your first 10 Routes here
    }
    Group {
        // ...the next 10 Routes here
    }
    // Etc for a maximum of 10 Groups.
}

Hopefully I explained this clearly enough. 😄

from swiftui-router.