Method nest

crates/bindings/src/http.rs:341–358

Causes requests which start with `path` to be processed by `sub_router`. `sub_router` will be used by stripping the leading `path` from the path of the request. Panics if `self` already has any handlers registered on paths which start with `path`. Panics if the `path` is [invalid](Self#paths).

(self, path: impl Into<String>, sub_router: Self)

    ///
    /// Panics if the `path` is [invalid](Self#paths).
    pub fn nest(self, path: impl Into<String>, sub_router: Self) -> Self {
        let path = path.into();
        assert_valid_path(&path);

        // FIXME: either this check is too restrictive, or the checks in the other methods are too lenient.
        // Do we want it to be the case that the `sub_router` effectively takes ownership of the whole route below `path`,
        // or just the routes it actually contains?
        if self.routes.iter().any(|route| route.path.starts_with(&path)) {
            panic!("Cannot nest router at `{path}`; existing routes overlap with nested path");
        }

        let mut merged = self;
        for route in sub_router.routes {
            let nested_path = join_paths(&path, &route.path);
            merged = merged.add_route(route.method, nested_path, route.handler);
        }
        merged
    }

    /// Combines all of the routes in `self` and `other_router` into a single [`Router`].
    ///