Rob Ede
Rob Ede
As you've noticed, `Scope`s match paths in a fundamentally different way to a flat route structure. In general, once a service has been matched the router will never consider services...
Here's a reasonably clean solution that allows you to keep the scopes and also re-use the generic device routes: https://www.rustexplorer.com/b/6kr5zk --- Using `Scope::configure` can help segment code in to modules...
I'll consider this particular issue closed when docs have satisfactory detail added though you may with to follow #414 and #2264 too.
Can you show an example of a route and handler setup that is surprising to you?
Can you try this code using the `awc` beta?
http2 page has moved to using rustls now
There isn't much we could have done about this. Nightly failures happen and libraries that opt in to using those unstable features automatically subscribe to dealing with these kinds of...
I haven't looked closely enough at other things other than the message you pasted: ``` error: could not compile `ahash` (lib) due to 1 previous error ``` `ahash` is at...
I guess you can only pin as far as the library itself does. Crates in the Rust ecosystem expect semver compatibility within a semver range. In this case, everything works...
@mkvalor there's no need, I'm right here :P